重新加载.net dll_.NET纯净的神话，重新加载

重新加载.net dll

An updated version of my Myth of .NET Purity rant is up on MSDN.  I recommend you show it to your boss if you're being force to justify why your solution isn't 100% .NET. 

MSDN上已更新了.NET纯度神话的更新版本。 如果您被迫证明为什么您的解决方案不是100％.NET，我建议您向老板展示。

Summary: Does a solution written for Microsoft .NET have to be 100% .NET? Scott Hanselman looks at how hybrid managed-unmanaged solutions are really the norm.

摘要：为Microsoft .NET编写的解决方案是否必须是100％.NET？ 斯科特·汉瑟曼(Scott Hanselman)着眼于混合托管与非托管解决方案的真正规范。

Here's a few choice quotes, IMHO: ;)

这是一些选择语录，恕我直言：;)

I've heard it said by many a CTO in many a technical briefing that, "We're planning to port our whole system to .NET." Why spend 18 months converting your application, so you can arrive at the endpoint you're already at?

我听说许多CTO在许多技术简报中都说：“我们正计划将整个系统移植到.NET。” 为什么要花18个月的时间转换您的应用程序，以便可以到达已经到达的端点？

The .NET Framework Library itself isn't "pure .NET," as it uses every opportunity to take full advantage of the underlying platform primitives.

.NET Framework库本身不是“纯.NET”，因为它利用一切机会来充分利用基础平台原语。

If Microsoft were to truly virtualize the machine, they would have marginalized their investment in the Windows platform.

如果Microsoft真正对计算机进行虚拟化，他们将在Windows平台上的投资边缘化。

翻译自: https://www.hanselman.com/blog/the-myth-of-net-purity-reloaded

重新加载.net dll