All geek questions in one place

Risk of migrating a website from .NET 2.0 to .NET 3.5

What is the inherent risk of updating a website from 2.0 to 3.5?

I know the functions provided to me during the upgrade process, just curious if there are any known problems that may appear during the upgrade.

those. Function X is used in this way and now behaves in a new way.

+3
source share
3 answers

The only major areas of problems I discovered 2.0-> 3.5 were found in Web.Config and centered around links to System.Web.Extensions 2.0. If you use the Visual Studio interface to change the version of your .NET project, VS will automatically fix most of the reference incompatibilities in your Web.config file.

As for the differences in the code, you will probably find that some methods that were deprecated with newer versions, but I never came across any direct violation.

Microsoft has a very strict backward compatibility compatibility standard so that they can minimize the impact of major updates.

+8
source

AFAIK , .NET 3.5: web.config. , SO.

,.NET 2.0, 3.0 3.5. ​​ , .

. 3 - - web.config.

+2

I had very few problems when I did this.

3.5 really works like 2.0 in IIS, so 3.5 is an extra feature.

Give it a crack and compilation should be fine.

+1
source

Source: https://habr.com/ru/post/1761523/

More articles:


All Articles