NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

multiple files to be copied

hi
I am trying to build a exe using the teststand deploy facility.
along with the installing process, i want certain ini files to be copied
to a specified folder & certain dll to another specified folder.

can this two task be acheived in a single exe,
how can i create the task in one exe using test stand
deploy option.
please guide me
regards
rags
0 Kudos
Message 1 of 7
(3,691 Views)
Hi rags,

Thanks for using the NI forums! 

The TestStand deploy utility will install on your target machine using the same file structure as specified in the workspace pane within your project.  To specify a particular file to be installed in a particular folder within your project, simply create that folder (by clicking on New Folder from the right-click menu of the parent folder to which you wish to add a child folder) and drag and drop your file there. Any file included in this workspace will be included in your deployment, even files not used by your project.

If you wish for your specified file's path to be located outside of your installing directory, then you can use custom installer commands to move these files from their installed paths within the project to your desired target system path. These commands are added in the TestStand Deployment Utility dialog box»Installer Options»Custom Commands...

Hope this helps!



Evan Prothro
RF Systems Engineer | NI

0 Kudos
Message 2 of 7
(3,669 Views)
I wanted to clarify a few things on my previous post, and add some more information.

1. Drag and drop functionality works within the workspace explorer only, not from the Windows environment into test stand. Files can be added to the project by clicking Add Files to Folder... from the right-click menu of the folder to which you want to add files within the workspace explorer.

2. The hierarchy within the workspace explorer is for your TestStand workspace organization only, the files within this heirarchy will still deploy to their default installation destinations. By default, the TestStand deployment will attempt to imitate the relative install paths that exist on your system. In order to change these default installation properties you can navigate to the Installer Properties section on the Distributed Files tab of the TestStand Deployment Utility dialog box.  by selecting a file in the Distributed Files: pane on the left and changing the Installation Destination and Installation Destination Subdirectory fields you can fully specify where you would like the file to be deployed.

This method obsoletes the need to use the custom commands I mentioned in my previous post, since it is much simpler and more straightforward.



Evan Prothro
RF Systems Engineer | NI

Message 3 of 7
(3,655 Views)

Hi Evanp,

I went thru the procedure you have suggested & i have an doubt incase , i used the Custom Command option, since my requirement is to install in

different folders, that would be fine, then my question would be while I uninstall how will the process deletes the files copied from custom command

inorder to complete the unistallation process.

regards

rags

0 Kudos
Message 4 of 7
(3,638 Views)
Hi rags,

Please see my 2nd post, as it outlines a much more efficient way to accomplish what you desire. This second post describes a method that avoids the use of custom commands and also will ensure that the uninstall process removes your files installed with specified, non-default paths.



Evan Prothro
RF Systems Engineer | NI

0 Kudos
Message 5 of 7
(3,632 Views)
Hi evanp
I have sucessfully build the installer following the procedure you
have mentioned above, but i am hedl up in another problem.
while i unistall, the filed copied thru the command option
is not unistalled. how can i over come this.
how to unistall the files copied thru custom command.
regards
rags
0 Kudos
Message 6 of 7
(3,583 Views)
Rags,

If you read my 2nd post, it outlines a method that avoids the use of custom commands, which as you have discovered will not reverse the effects of the commands during uninstall.  The way outlined in my 2nd post is the recommended method to accomplish what you wish, and should solve the problem you are having.

Thanks.



Evan Prothro
RF Systems Engineer | NI

0 Kudos
Message 7 of 7
(3,434 Views)