We develop a .Net component that, when hosted in Internet Explorer, requires Full Trust on the client's computer because we use P/Invoke to invoke unmanaged functions. In earlier versions of .Net (2.0 and 3.5) we required the user to modify their .Net
framework security settings to allow our assembly to be loaded and executed.
To do this, we provided instructions on how to modify the security settings in one of three ways:
- using the .Net Framework Configuration Tool
- using caspol.exe utility with this line of code:
caspole.exe -polchgprompt off -addgroup 1 -site
is their actual site name)
- Using an MSI to configure a site policy
Now, with .Net 4, some of our users (who themselves are developers) want to use our component in .Net 4 targeted applications (on computers that do not have older versions of the framework) but they are reporting that they cannot modify the security settings
as they did before. Obviously this is because of changes to CAS with the release of .Net 4.
With the new security model, how do we get a .Net 4 assembly to run in Full Trust when it's hosted in Internet Expl
View Complete Post