My team is writing an ASP.Net webapp in VS2008 targeting .Net3.5 SP1. Some of us have the .Net runtime version 2.0.50727.3082 installed, and others have 2.0.50727.3053. Everyone's Windows Update reports no available updates, even the people with the lower build number, and I wouldn't care at all except that all .designer.cs files include the runtime version in their header, and the differing runtime versions cause spurious changes in source control. Installing the very latest .Net3.5 setup from Microsoft doesn't address the issue - the .3053 version is still installed, even after the runtime is 'repaired'.
我的团队正在VS2008中编写一个针对.Net3.5 SP1的ASP.Net webapp。我们中的一些人安装了.Net运行时版本2.0.50727.3082,其他人有2.0.50727.3053。每个人的Windows Update都没有报告可用的更新,即使编号较低的人也没有,除了所有.designer.cs文件都在其标题中包含运行时版本之外我完全不关心,不同的运行时版本会导致虚假的更改源控制。从Microsoft安装最新的.Net3.5安装程序无法解决问题 - 即使在运行时“修复”之后,仍然安装.3053版本。
In the short term, how do I upgrade from .3053 to .3082, and in the medium term how do I ensure my entire team is on the same .Net runtime version?
在短期内,我如何从.3053升级到.3082,在中期内如何确保我的整个团队使用相同的.Net运行时版本?
3 个解决方案
#1
2.0.50727.3082 is the version of the .NET 2.0 runtime installed with .NET 3.5 sp1. Make sure that all of your users correctly install .NET 3.5 SP1, and they should get that version.
2.0.50727.3082是随.NET 3.5 sp1一起安装的.NET 2.0运行时版本。确保所有用户都正确安装.NET 3.5 SP1,并且他们应该获得该版本。
*.3053 was installed with .NET 2.0 sp2's standalone install. You could try uninstalling this, then installing 3.5sp1 again (since that installs its own version of .NET 2.0 sp2 - the one with the higher version number).
* .3053与.NET 2.0 sp2的独立安装一起安装。您可以尝试卸载它,然后再次安装3.5sp1(因为它安装了自己的.NET 2.0 sp2版本 - 具有更高版本号的版本)。
#2
You can build a Virtual Machine and install there all the tools your team needs to share then distribute it among your teammates.
您可以构建一个虚拟机,并在那里安装您的团队需要共享的所有工具,然后将其分发给您的团队成员。
#3
Reed's answer is good (+1), but the question also indicates the general need for some desktop standardization. We use dev. images and then make official team posts regarding when and how to install updates. Images are not always practical, so we have complete "getting started" documents for developers that ensure that they install only approved updates in a manner and order specified in the doc. The system breaks down with consultants who generally want to use their own machines (laptops). But, I've found that keeping environments as synchronized as possible cuts down a lot of "works on my machine" type issues and also cuts down on developer helping developer troubleshoot why things don't build or work correctly on their PC.
Reed的答案很好(+1),但问题也表明了一些桌面标准化的普遍需求。我们使用dev。图像,然后制作关于何时以及如何安装更新的官方团队帖子。图像并不总是实用的,因此我们为开发人员提供了完整的“入门”文档,以确保他们只按照文档中指定的方式和顺序安装已批准的更新。系统因一般想要使用自己的机器(笔记本电脑)的顾问而崩溃。但是,我发现保持环境尽可能同步会减少许多“我机器上的工作”类型问题,同时也减少了开发人员帮助开发人员解决为什么事情无法在PC上构建或正常工作的问题。
The downside is "one license all license" and I must have ReSharper, so everybody gets ReSharper. :)
缺点是“一个许可证所有许可证”,我必须有ReSharper,所以每个人都得到ReSharper。 :)
#1
2.0.50727.3082 is the version of the .NET 2.0 runtime installed with .NET 3.5 sp1. Make sure that all of your users correctly install .NET 3.5 SP1, and they should get that version.
2.0.50727.3082是随.NET 3.5 sp1一起安装的.NET 2.0运行时版本。确保所有用户都正确安装.NET 3.5 SP1,并且他们应该获得该版本。
*.3053 was installed with .NET 2.0 sp2's standalone install. You could try uninstalling this, then installing 3.5sp1 again (since that installs its own version of .NET 2.0 sp2 - the one with the higher version number).
* .3053与.NET 2.0 sp2的独立安装一起安装。您可以尝试卸载它,然后再次安装3.5sp1(因为它安装了自己的.NET 2.0 sp2版本 - 具有更高版本号的版本)。
#2
You can build a Virtual Machine and install there all the tools your team needs to share then distribute it among your teammates.
您可以构建一个虚拟机,并在那里安装您的团队需要共享的所有工具,然后将其分发给您的团队成员。
#3
Reed's answer is good (+1), but the question also indicates the general need for some desktop standardization. We use dev. images and then make official team posts regarding when and how to install updates. Images are not always practical, so we have complete "getting started" documents for developers that ensure that they install only approved updates in a manner and order specified in the doc. The system breaks down with consultants who generally want to use their own machines (laptops). But, I've found that keeping environments as synchronized as possible cuts down a lot of "works on my machine" type issues and also cuts down on developer helping developer troubleshoot why things don't build or work correctly on their PC.
Reed的答案很好(+1),但问题也表明了一些桌面标准化的普遍需求。我们使用dev。图像,然后制作关于何时以及如何安装更新的官方团队帖子。图像并不总是实用的,因此我们为开发人员提供了完整的“入门”文档,以确保他们只按照文档中指定的方式和顺序安装已批准的更新。系统因一般想要使用自己的机器(笔记本电脑)的顾问而崩溃。但是,我发现保持环境尽可能同步会减少许多“我机器上的工作”类型问题,同时也减少了开发人员帮助开发人员解决为什么事情无法在PC上构建或正常工作的问题。
The downside is "one license all license" and I must have ReSharper, so everybody gets ReSharper. :)
缺点是“一个许可证所有许可证”,我必须有ReSharper,所以每个人都得到ReSharper。 :)