I have an unmanaged application that hosts the CLR. This application could
reside on a machine that has a security policy which prevents standalone
managed code from executing under the same conditions. For example, the
unmanaged executable (and supporting managed assemblies) could be located on
a network share. Is there a way I can override the security policy in place
on the machine when I am hosting the CLR? It seems odd that from unmanaged
code I have full access, but once I try to use hosted managed code I am
restricted.