Are there any .NET Framework 3.5. Deployment Alerts?

Question

What level of concern should I apply to deploy the .NET framework 3.5 to a production application server that currently hosts about 20 .NET framework 2.0 applications?

I have resistance to my request for deploying the .NET framework 3.5 in our environment. We do not have confidence in the possibility of a regression test, and we do not have the available resources for confidence in checking each application.

I understand that the .NET framework XX, as the main goal of the project, is built and proven to allow deployment of 1.0, 1.2, 2, 3, 3.5, etc. on the same machine with a high degree of confidence that the interaction between versions will not violate an earlier version.

I tried to find the “hacked changes” that are being reported in the IT community, and very few examples have been found so far, and therefore I tend to insist on deploying this runtime environment with minimal testing.

What is your perceived degree of concern about this approach to deploying .NET 3.5 in this situation.

Answer 1

My level of anxiety is very low. The only way the 3.5 framework interacts with existing 2.0 applications is through the service pack that applies to CLR 2.0 during the 3.5 installation. Namely, Service Pack 1. Therefore, after installation, all your previous applications will start working on CLR 2.0SP1 and CLR 2.0.

So, is this really a question of how much trust do you have in the service pack?

Here is a link to the service pack and a list of fixed bugs. All bug fixes to some extent change and can affect the behavior of the application (otherwise why fix it?).

• http://support.microsoft.com/kb/945757

Answer 2

.Net 2.0 is just a subset of .Net 3.5

Both are built on top of CLR 2.0.

3.0 Foundation libraries (WF, WCF, WPF) were added, and 3.5 was the next deployment of additional functions . In general, you should not have any problems if you did not do something completely crazy on your machines.

Answer 3

I understand your concern and usually recommend doing as many tests as you can on a server in a non-production environment.

But having said that, the basic components of the .NET 3.5 runtime are the same as in .NET 2.0. Version 3.5 is essentially .NET v2.0 with additional libraries on top.

As you say, the framework is designed for coexistence, so everything should be in order.

Of course, we did not have any problems arising in our living environment.

Disclaimer: all of the above is only from my experience - please do not blame me if everything goes wrong !; ABOUT)

Answer 4

Multiple versions of dotnet can reside on the same computer, and a point network node actually retains its target structure in its manifest. Therefore, if the application is compiled with version 2.0 or later, and this version exists on your computer, then there is absolutely no problem. This is what the dotnet frame is aiming for first place. Running side by side and fixing a problem with DLL addons.

However, upward compatibility has never been a problem ... if the assembly was compiled with version 2.0, it will work fine in later versions ... However, if some thing still goes wrong, you need to blame MS: P ..

In the case of new versions, fortunately, we are mature enough to provide only outdated verification at compile time. There will be no problems during the execution process.

Errors that appear after adding new functionality to the frame (as you mentioned regression testing your application) about these conditions ... well, there is always a chance, albeit a very rare one. However, if you go in the direction of a parallel implementation of the dotnet infrastructure, the assembly will be loaded and run in the target environment if it exists on the machine.

Answer 5

As long as I agree with everyone here, I would add one comment. If you install .NET 3.5 Service Pack 1 (SP1), you get additional permissions that are automatically inserted into the machines, which allows the .NET network share code to work with full permissions, just as if they were running on a local hard drive, If this is a problem for you, then you may need to limit access rights.