如果您想要 .NET 2.0 中的 LINQ to Objects，LINQBridge 是您的朋友。 对于其他问题，我强烈建议寻找第三方实现或升级部署计算机上的框架版本。
You definitely, definitely shouldn't start redistributing DLLs from one framework version to another.
For one thing it may well be illegal (even or possibly especially using Reflector to extract source) - but more importantly, you've then got a bit of code which was designed and written for one version of the framework running against another. Who knows if they've relied on a bugfix in mscorlib which was only implemented in .NET 3.5?
If you want LINQ to Objects in .NET 2.0, LINQBridge is your friend. For other issues, I would strongly recommend looking for a third party implementation or upgrading the version of the framework on the deployment machine.
Why would you need to distribute those dll's? You need an installation of the .Net framework on your client's machine anyway. That should include all relevant Microsoft dll's.
AFAIK a .Net ap can not be run on a machine without the framework, so you need it anyway.
Edit I just had a look at the .NET Framework 1.1 Redistributable EULA (could not find the one for 3.0 in Google). It does not specificly allow what you are proposing, so my guess is that you may not do it.
发布评论
评论（3）
您绝对、绝对不应该开始将 DLL 从一个框架版本重新分发到另一个框架版本。
一方面，它很可能是非法的（甚至或可能特别使用 Reflector 来提取源代码） - 但更重要的是，您已经获得了一些为一个版本设计和编写的代码框架与另一个框架运行。 谁知道他们是否依赖于 mscorlib 中仅在 .NET 3.5 中实现的错误修复？
如果您想要 .NET 2.0 中的 LINQ to Objects，LINQBridge 是您的朋友。 对于其他问题，我强烈建议寻找第三方实现或升级部署计算机上的框架版本。
You definitely, definitely shouldn't start redistributing DLLs from one framework version to another.
For one thing it may well be illegal (even or possibly especially using Reflector to extract source) - but more importantly, you've then got a bit of code which was designed and written for one version of the framework running against another. Who knows if they've relied on a bugfix in mscorlib which was only implemented in .NET 3.5?
If you want LINQ to Objects in .NET 2.0, LINQBridge is your friend. For other issues, I would strongly recommend looking for a third party implementation or upgrading the version of the framework on the deployment machine.
我确信您认为 .NET 上的 Microsoft 许可绝对是非法的
I'm sure that you idea absolutely illegal for Microsoft license on .NET
为什么需要分发这些 dll？ 无论如何，您都需要在客户端计算机上安装 .Net 框架。 这应该包括所有相关的 Microsoft dll。
据我所知，.Net ap 无法在没有框架的机器上运行，所以无论如何你都需要它。
编辑
我刚刚查看了 .NET Framework 1.1 可再发行 EULA （在 Google 中找不到 3.0 的版本）。 它没有明确允许您提出的建议，所以我的猜测是您可能不会这样做。
附：
肛门;-)
Why would you need to distribute those dll's? You need an installation of the .Net framework on your client's machine anyway. That should include all relevant Microsoft dll's.
AFAIK a .Net ap can not be run on a machine without the framework, so you need it anyway.
Edit
I just had a look at the .NET Framework 1.1 Redistributable EULA (could not find the one for 3.0 in Google). It does not specificly allow what you are proposing, so my guess is that you may not do it.
p.s.:
IANAL ;-)