Can I leave the Deployment Subdirectory blank

[SeanJ]

Hi,

I'm having trouble deploying a system the way I want.

I basically want a result and application folder in the root drive after deployment.

e.g.

c:\application

c:\result

When I try to deploy if I don't fill in an application subdirectory I get the following error.

***************************************
The build contains one or more invalid paths:
Invalid Default Installation Subdirectory: ""
+++++++++++++++++++++++++++++++++++++++

Ok, I recognise it's easy to copy and paste but unfortunately there are some other files I want to deploy that go in other folders.  It all starts to look very unprofessional if I start telling a customer, yeah cut that folder, paste it in this folder, now cut that one paste again and this one etc.

Does anyone know if there is a way of leaving the installation subdirectory blank?

[Teds]

I think that is a known issue since TestStand 4.0, I found it within the TestStand 4.2.1 known issues link.

*****************************************************************

Leaving the Default Installation Subdirectory field empty in the Installer Options tab of the TestStand Deployment Utility results in a build error
If you leave the Default Installation Subdirectory field empty in the Installer Options tab of the TestStand Deployment Utility because you want the files to install in the base directory, the deployment utility returns the following message when you attempt to build: "The build contains one or more invalid paths: Invalid Default Installation Subdirectory: """

Workaround: Place a period in the Default Installation Subdirectory field to install files in the base directory.

Reported Version: 4.0

Resolved Version: N/A

Added: 12/11/2009

***************************************************************

It looks like you can just use a period.  I was going to suggest using a batch file to move your installed files to the correct directory but I think the above Workaround should work.

Thanks,

PH