Menu
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'.
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?
945
NET Framework are the Common Language Runtime and the . NET Framework Class Library. The Common Language Runtime (CLR) is the execution engine that handles running applications. It provides services like thread management, garbage collection, type-safety, exception handling, and more.
Microsoft designed the . NET Framework so that multiple versions of the framework can be installed and used at the same time. This means that there will be no conflict if multiple applications install different versions of the . NET framework on a single computer.
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.
*.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).
171
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
