tags:

views:

103

answers:

1

I'm attempting to dynamically load some (purchased) assemblies from resource streams in a C# program during an MSI installation routine, but I'm getting "Unverifiable code failed policy check".

I read some tips online about compiling the embedded assembly with /clr:safe, but I don't have that option. Is there a way to work around this policy check?

Thanks.

+1  A: 

The only way to load unverifiable code is from a full trust process (or maybe app domain) with verification disabled.

EDIT: I'm not making this up, one of the C# language designers said "Unverifiable code requires full trust and is generally to be avoided"

Ben Voigt
reason for downvote?
Ben Voigt
Wasn't me. I would like to know too! Sounds like they would have a better suggestion. I'll counter it due to the lack of an explanation
uosɐſ