.NET Framework 3.5 SP1和Windows Update上的更新

The .NET Framework 3.5 SP1 included a bunch of new features, but as a Service Pack it also included a number of bug fixes and many improvements. These fixes included all aspects of the .NET Framework from ASP.NET to WPF and the CLR.

.NET Framework 3.5 SP1包括许多新功能，但作为Service Pack，它还包含许多错误修复和许多改进。 这些修复包括从ASP.NET到WPF以及CLR的.NET Framework的各个方面。

.NET Framework 3.5 SP1会破坏我的2.0应用程序吗？ (Will the .NET Framework 3.5 SP1 break my 2.0 apps?)

Almost certainly not.

几乎可以肯定不是。

为什么不？ (Why Not?)

Remember that 3.5 (and 3.0 before it) all have the 2.0 CLR at their core. If you want excessive detail on this, I've got it. Because the 2.0 CLR is the engine underneath and 3.0 and 3.5 are primarily additive*, there's inherently high application compatibility between these releases.

请记住，3.5(及其之前的3.0)的核心都是2.0 CLR。 如果您想对此进行详细说明，我已经掌握了。 因为2.0 CLR是其引擎，而3.0和3.5主要是加法*，所以这些版本之间固有地具有很高的应用程序兼容性。

Realize that 2.0, 3.0 and 3.5 are not different products, no matter what anyone says. They are not different "Side By Side" releases, like 1.x and 2.0 were. They are evolutionary; if anything, our naming could have been better (you think?), but rather each adds functionality to the one before it. They are really additive releases to the same core product.

认识到2.0、3.0和3.5并不是不同的产品，无论别人怎么说。 它们与1.x和2.0一样，与“ Side By Side”版本不同。 它们是进化的； 如果有的话，我们的命名本来可以更好(您认为呢？)，但是每个命名都为之前的命名增加了功能。 它们实际上是同一核心产品的附加发行版。

但是，我遇到了一个极端情况…… (But, I've hit an edge case…)

We’re committed to application compatibility. However you may have heard or reported issues or bugs around 3.5 SP1 and I’ll go into how we’re dealing with those below. Most of these are corner-case/edge-case situations.

我们致力于应用程序兼容性。 但是，您可能已经听说或报告了有关3.5 SP1的问题或错误，我将在下面介绍如何处理这些问题。 其中大多数是极端情况/边缘情况。

It may be cold comfort when it’s your bug and your company and it sounds like a marketing line, but it’s true. There are a lot of resources working to minimize impact to you.

当这是您的虫子和您的公司时，可能会感到很冷淡，听起来像是一条营销路线，但这是事实。 有很多资源可以最大限度地减少对您的影响。

I’ve now been on both sides, when working in a large ISV and trying to get a hotfix, and now on the inside trying to keep compatibility while keeping things secure and correct. There is a massive amount of unit and integration testing that goes into the .NET Framework (that includes all technologies under that umbrella).  That means that every effort is made not to break stuff. That’s why Visicalc still runs nicely on my Vista x86 machine (although I can’t run OS 9 apps on OS X anymore, interestingly ;) ) 

在大型ISV中工作并尝试获取修补程序时，我现在一直处于两面，现在在内部又在保持兼容性的同时试图确保事物的安全性和正确性。 .NET Framework中有大量的单元和集成测试(包括该伞下的所有技术)。 这意味着将尽一切努力不破坏东西。 这就是为什么Visicalc在我的Vista x86机器上仍然可以很好地运行的原因(有趣的是，尽管我不再能够在OS X上运行OS 9应用程序；))

Software testing is a combinatorial problem, and as such all software has bugs, but sometimes when a bug comes back it’s called a “regression.” That means it was fixed before, and now it doesn’t. Sometimes folks call a new bug a regression their software worked before and it doesn’t now. This might be because they relied on an incorrect behavior that was later corrected, or that it was just a bug.

软件测试是一个组合问题，因此所有软件都存在错误，但有时当错误返回时，称为“回归”。 这意味着它以前是固定的，现在没有。 有时人们称新错误是他们的软件以前使用过的回归，而现在则不行。 这可能是因为他们依赖的错误行为后来得到纠正，或者仅仅是一个错误。

It IS possible that something could break, so as with all SP’s you should do compatibility testing to make sure you’re not hitting an edge case.  If you are affected by a bug at some point, we’re trying to get you a very fast response. Notice in the table below there’s a “How Found” column. You can report on Forums, contact PSS or use Connect to report bugs.

可能会破坏某些东西，因此对于所有SP，都应进行兼容性测试，以确保不会遇到任何问题。 如果您在某个时候受到错误的影响，我们正在努力为您提供快速的响应。 请注意，下表中有一个“如何找到”列。 您可以在论坛上报告，联系PSS或使用Connect报告错误。

何时将.NET Framework 3.5 SP1推送到Windows Update？ (When will the .NET Framework 3.5 SP1 be pushed to Windows Update?)

Later this year, probably November-ish, the .NET Framework 3.5 SP1 will begin show up on Windows Update in a rolling and throttled fashion so that all machines that have .NET 2.0 or higher will be automatically upgraded to 3.5 SP1.

今年晚些时候(大概是11月)，. NET Framework 3.5 SP1将以滚动和限制方式开始出现在Windows Update上，以便所有具有.NET 2.0或更高版本的计算机都将自动升级到3.5 SP1。

If you’re an ISV