由网友(随风荡)分享简介：对于我目前的项目中，我们使用了一些CLR 2为主的混合模式组件。For my current project, we're using some CLR 2 based mixed mode assemblies.为了到.NET 4针对性装配中使用这些从，我就知道你要添加 useLegacyV2RuntimeAct...

对于我目前的项目中，我们使用了一些CLR 2为主的混合模式组件。

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

为了到.NET 4针对性装配中使用这些从，我就知道你要添加 useLegacyV2RuntimeActivati​​onPolicy = TRUE 到<startup>内的app.config 元素。

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.

据我所知，这将改变激活策略，导致使用CLR的支持的最高版本，加载这些混合模式组件。

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?

推荐答案

嗯，当然，你会运行一个CLR版本，它从未测试过的应用程序。微软做了伟大的工作，保持后向兼容。但微软的经理失去了几天的电子邮件访问.NET程序升级后的情况是有名的。线程池时机略有不同，暴露在写实习程序的线程比赛。不能谷歌现在的链接。

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.