Repercussions of enabling useLegacyV2RuntimeActivationPolicy?
Posted
by Reed Copsey
on Stack Overflow
See other posts from Stack Overflow
or by Reed Copsey
Published on 2010-02-13T00:38:38Z
Indexed on
2010/03/18
2:41 UTC
Read the original article
Hit count: 1023
For my current project, we're using some CLR 2 based mixed mode assemblies.
In order to use these from within a .NET 4 targetted assembly, I know you have to add useLegacyV2RuntimeActivationPolicy=true
to the <startup>
element within app.config.
I understand that this changes the activation policy, causing these mixed-mode assemblies to be loaded using the highest supported version of the CLR.
However, are there any side effects to doing this? What potential issues should I watch for when enabling the non-default activation policy?
© Stack Overflow or respective owner