How to ensure that my entire team has the exact same version of .Net runtime?

Question

My team is writing an ASP.Net web application in VS2008 aimed at .Net3.5 SP1. Some of us have the .Net 2.0.50727.3082 version installed, while others have 2.0.50727.3053 . Every Windows Update lacks available updates, even people with a lower build number, and I would not care, except that all .designer.cs files include the version of the execution at the time of their header, and different versions of the execution cause false changes in source control. Installing the latest version of .Net3.5 from Microsoft does not fix the problem - the .3053 version is still installed, even after the runtime is “restored”.

In the short term, how can I upgrade from .3053 to .3082, and in the medium term, how can I ensure that my entire team is in the same version of the .NET runtime.

Answer 1

2.0.50727.3082 is a version of the .NET 2.0 runtime installed with .NET 3.5 sp1. Make sure that all your users have correctly installed .NET 3.5 SP1, and they should get this version.

*. 3053 was installed with a standalone installation of .NET 2.0 sp2. You can try to remove this and then install 3.5sp1 again (since it installs its own version of .NET 2.0 sp2 - the one that has the higher version number).

Answer 2

You can create a virtual machine and install all the tools your team should share there, and then distribute them to your teammates.

Answer 3

Reed answer is good (+1), but the question also points to the general need for some standardization of the desktop. We are using dev. and then post official messages about when and how to install updates. Images are not always practical, therefore, we have complete "initial" documents for developers, which guarantee that they will install only approved updates in the order and order specified in the document. The system breaks down with consultants who usually want to use their own computers (laptops). But I found that keeping the environment as synchronized as possible reduces the number of “works on my machine” problems, and also reduces the developer’s work, helping the developer troubleshoot why they don’t build and work correctly on their PC.

The downside is “one license for all licenses”, and I have to have ReSharper, so everyone gets ReSharper. :)