Assembly Trust

23 Mar 2006 3:00 PM

Elio Gonzalez

Hi,

    I'm currently deploying a 1.1 .net dll assembly which is installed on a
shared folder on a file server along with a legacy application. The
clients run the .exe from the server. The .exe calls the .net .dll via
interop.

    In our environment we had to increase the trust for the assembly in
each client (or increase the trust of the server) for it to work
correctly.

    It currently works perfectly on clients with only the .NET 1.1 runtime
installed. However, when a client installs the .NET 2.0 runtime it no
longer works. It seems the 2.0 security settings are being used instead
of the 1.1 settings. This wouldn't be a huge issue, but it seems that I
can't change the security settings on the 2.0 framework because it
doesn't come with the "Microsoft .NET Framework Configuration" shortcut
in the control panel.

    Is there any easy way to have them change this other than installing
the .NET 2.0 SDK (which installs the control panel applet) ?

Thanks,

Elio

24 Mar 2006 12:53 PM

oldbear

Hi

You can create a .bat file for each user that calls the CASPOL command line
tool:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/html/cpgrfCodeAccessSecurityPolicyUtilityCaspolexe.asp

Send this to the user, and they can click on the file to set the relevant
permission.

Group policy in Active Directory allows scripts to be applied to machines,
but only when they are rebooted.

Hope this helps

Chris Seary