.NET classes not visible when executable is placed on a shared drive

[jackmanlin]

Hi all

I have an issue where the public classes of my executable are all not visible when the executable is placed in my shared drive. They are visible when placed on a local drive. I am using TestStand 4.1.0.228.

I have tried the following:

Turned off the virus scanner

Made sure I have the correct permissions

Tried doing the same task on my colleague's computer with exactly the same settings

Thanks

[jackmanlin]

I would like to add that the code was written in Delphi Prism (Delphi pascal in a .NET environment). When a test program was written in c# public classes could be seen

[dug9000]

.NET generally considers code on network drives to be only partially trusted, so it's possible that that is affecting how things are working for you, at least if your entrypoints require privileges that aren't available to partially trusted code. But in that case I would have expected it to show the entrypoints, but give an error if you tried to call them.

By "not visible" do you mean not visible in the .NET adapter?

Also, since this problem is only happening with Delphi and not C#, you might want to contact the company that makes Delphi and see if they know what the problem might be.

Hope this helps,

-Doug

[jackmanlin · Accepted solution]

I've looked at my code again and I'm glad to say I've solved this problem. Like you said it has to do with partially trusted callers. At the start of my development cycle i added these two lines into my assembly file:

[assembly: System.Security.AllowPartiallyTrustedCallers]

[assembly: System.Security.Permissions.PermissionSet(System.Security.Permissions.SecurityAction.RequestMinimum, Name:="FullTrust")]

However, this was messing with the access. Since these two lines were added before the Christmas break I can't remember exactly the chain of events that prompted me to add them. However, now I've commented it out and all the public classes in the .NET adaptor are visible.

Thanks for pointing me in this way.

I am currently writing up a document detailing my process of using .NET in TestStand. Hopefully my company will allow me to release the document so others can gain knowledge from this information. Fingers crossed

[Danceman]

Hello Jackmanlin,

      I am glad to hear that worked,  I want to also thank you for wanting to post the documentation so others can learn as well.

Dan 

[dug9000]

Keep in mind the .NET adapter changed considerably in TestStand 2010, so your document might not apply to TestStand 2010 and higher in some ways, depending on the sort of content you are writing. If you are using .NET heavily from TestStand, you might consider trying out TestStand 2010sp1 if it might be possible for you to use that version.

-Doug

[jackmanlin]

Got permission to upload the doc :). Link below:

https://docs.google.com/open?id=0B-6zYYgk88jCYTM1N2JjNDItZWY0NC00MjhiLThiMWYtZDIwZmI4YWRhMThh

[silversurfer]

Are you able to repost this document? I think I may have a related issue. Thanks in advance!