.NET Security Exception and .NET policies

[nelsonbrodyk]

Hey All,
When I try and run an application I have installed locally, it works fine. At some point I need to download another dll and run that dll. When I try, this happens:

System.Security.SecurityException: Request for the permission of type 'System.DirectoryServices.DirectoryServicesPermiss ion, System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' failed.


Now if I go to my .NET Framework 2.0 settings in Control Panel -> Administrative Tools -> .Net 2.0 -> Runtime security -> Code groups -> right click properties -> and set "Permission Set" to Fulltrust it works fine.

The issue is I will be installing this application, and I do not want to have to make users set their permission on every machine. Is there a nicer way to handle this, either through code, or by somehow getting the dll's I want to run to not throw a security exception?

Thanks!

[Plater]

If there is I would LOVE to hear it. So far I have not found anyway to do it.

[nelsonbrodyk]

If there is I would LOVE to hear it. So far I have not found anyway to do it.

Yikes...that's what I was hoping not to hear. Would signing the dlls or the application or both somehow make them trusted?

I can see the reason for this, they don't want people being able to download malicious code and execute it, but this also stops a lot of legitimate setups.

[Plater]

If you can manage to make your ENTIRE application strongly named (that means like no COM objects) then yes I think you can get it to work without changing the default .net security policies

[nelsonbrodyk]

I don't think we are using any COM objects. Atleast that I know of. How can we make this happen?

[Plater]

I used the wrong lingo earlier (corrected). Strongly Named Assembly is what you are going for I believe.
http://msdn.microsoft.com/en-us/library/wd40t7ad.aspx