NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Deployed file is not writeable

I have an issue where my deployed test system is deploying a ASCII file (TCL script) that is supposed to get dynamically edited by a LabVIEW VI durring test.  The issue is that Windows 7 is not allowing this file to be edited because if its security setting and where it is deployed to (the program files directory).  Is there a way to deploy this file so I don't have to go find it after install and edit the security on the file post deploy?  I think LabVIEW application builder has some checkbox to do this, does TestStand have the same thing?

 

As a side note, I thought I could just deploy this file to a different directory but I am not satisfied with TestStand's choses of Installation Directories.  I think that it is missing the option to deploy to the ProgramData directory.

 

Thanks,

Paul

0 Kudos
Message 1 of 2
(3,092 Views)

I agree 100% that it would be nice to have the Program Data folder as an option in the TestStand folder. ( maybe fill out an Idea Exchange)

 

We put our writable files in the Application Data folder: TestStand Data Application Directory

 

Then under there I will have the deployment utility create a folder that is specific for the Workspace I am deploying.

 

The sucky thing is that you have to have your search directories point to it.

 

Another option is to set C: as your base and then you can build off of it in your distribution list.

 

Hope this helps,

 

jigg
CTA, CLA
testeract.com
~Will work for kudos and/or BBQ~
0 Kudos
Message 2 of 2
(3,084 Views)