Home/ Questions/Q 621127
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T18:50:26+00:00

For my current project, we’re using some CLR 2 based mixed mode assemblies. In

  • 0

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?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Well, sure, you’ll be running the app with a CLR version it has never been tested against. Microsoft does a great job keeping it backwards compatible. But the case of Microsoft managers losing email access for a few days after a .NET upgrade is famous. The threadpool timing was slightly different, exposing a threading race in a program written by an intern. Can’t google the link right now.

    • 0