Hi all,
I am developing a TestStand program using a .NET DLL for UUT communication. When testing the .NET DLL I noticed that the DLL does not work when called from a network share. Since all our test programs are deployed to a network share, the first steps of the ProcessSetup sequence copy the DLL from the deployed test program on the network share to an absolute path on the C:\ drive. Copying the DLL file works.
In my test program I adjusted all the steps using the DLL with the absolute path to the DLL on the C:\ drive. Using the sequence editor, this works perfectly. When I deploy the test and run it on another computer, I get the error message:
Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib,Version=2.0.0.0,Culture=neutral,PublicKeyToken=b77a5c561934e089' failed.
If I open the deployed *.seq file, the paths to the DLL are all absolute as set in the sequence editor. When I search for the DLL using ProcExp, I see that the DLL from the network share is used. Why is the absolute path neglected? How can I force TestStand to use the absolute path?
A topic I found via the error message proposed to recompile the DLL with a strong name. Doing this results in the same error message.
Using TestStand version 4.1
Thanks in advance,
Stef