.NET 3.5的DLL在.NET 4.0应用程序的任何问题 [英] .Net 3.5 Dll's in a .Net 4.0 application any issues
问题描述
我们正计划将它使用企业库4.1，它使用的.Net 3.5在.NET 4.0中的Web应用程序的传统应用程序。
We are planning to move a legacy application which uses enterprise library 4.1 which uses .Net 3.5 in a .Net 4.0 web application.
我们想知道这会造成任何性能问题？将在不同的.NET 3.5 code运行 应用程序池？
We are wondering will this cause any performance problems? Will the .net 3.5 code run in a different application pool?
推荐答案
我终于找到了答案。性能问题我previously提到了我的团队发现是由于别的东西。不加载.NET 3.5的.NET 4.0应用程序域。
I have finally found answer to this. The performance problem I previously mentioned my team discovered is due to something else. Not loading .NET 3.5 on .NET 4.0 App Domain.
看完这篇文章： <一href="http://msdn.microsoft.com/en-us/magazine/ee819091.aspx">http://msdn.microsoft.com/en-us/magazine/ee819091.aspx
在进程内的SxS没有解决不了的 所面临的兼容性问题 库开发。任何图书馆 通过直接加载 应用 - 通过直接或者 引用或的Assembly.Load - 会 继续直接加载到 运行时的AppDomain中 应用程序加载它。意即 如果一个应用程序被重新编译 以针对.NET Framework 4的运行 运行时，仍然具有从属 构建在.NET 2.0组件， 这些家属将加载在.NET 4运行时也是如此。因此，我们仍 建议测试您的库 反对的所有版本，[S] 框架你想支持。这是 我们已经持续的原因之一 保持我们高的落后的水平 兼容性。
In-Proc SxS does not solve the compatibility problems faced by library developers. Any libraries directly loaded by an application--either via a direct reference or an Assembly.Load--will continue to load directly into the runtime and AppDomain of the application loading it. This means that if an application is recompiled to run against the .NET Framework 4 runtime and still has dependent assemblies built against .NET 2.0, those dependents will load on the .NET 4 runtime as well. Therefore, we still recommend testing your libraries against all version[s] of the framework you wish to support. This is one of the reasons we have continued to maintain our high level of backward compatibility.
那么，有没有问题，加载.NET 3.5程序集直接到.NET 4.0的应用程序无需重新编译成.NET 4.0。
So, there's no problem loading .NET 3.5 assemblies directly into .NET 4.0 apps without recompiling them into .NET 4.0.
这篇关于.NET 3.5的DLL在.NET 4.0应用程序的任何问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
