TestStand should use Workspace and Projects properly when determining the folders and files used for deployment. It should not default to reproducing the on disk source structure for your deployment.
I would expect the Project Folder and its contents to be the ROOT of my deployment placed in the C:\ProductionSW\ folder. My resulting installer should create C:\ProductionSW\ProjectFolder\
However the Distributed File Tree Views show:
View Workspace
View Source
View Build Preview
By default when I build the deployment it installs my software at C:\ProductionSW\Development\ProjectFolder\
The Development folder is not in the workspace or project. It is not referenced in any of the source files (as all paths are relative). I understand why it's in the View Source as that's where it resides on disk. However, the workspace/project should be used as the basis for the deployment not where things are on disk.
The source starts at ProjectFolder and that is what I expect to be deployed to my Default Installation Base Directory\Default Installation Subdirectory folder.
If the workspace and project aren't used to define your project code then what good are they in the Deployment Utility?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.