Geek Answers Handbook

Traps for converting .net 1.1 solution to .net 2.0

In this question, superwiren asks about the pitfalls for converting a .net 2.0 solution to .net 3.5.

What about .net 1.1 to.net 2.0?

Is 2.0 compatible with 1.1?

+3
source share
4 answers

I think it depends on your code, the best option is to do a test run and see what errors it will generate. I do not think .NET 2.0 is fully backward compatible, although they claim to be.

Common problems and solutions for conversion

compatibility from 1.1 to 2.0

+3
source

I worked on several conversions of ASP.NET 1.1 to 2.0 (medium-sized sites), and we found that the Visual Studio Conversion Wizard made everything quite simple. We did not encounter incompatibility issues, and the only thing that we really changed was to replace obsolete api calls with new functions. I would suggest you just take a picture.

+1
source

No, it is not. There have been many changes in version 2.0, but depending on how your application has been encoded, this may not affect everyone. Here is a document with links to all changes from 1.1 to 2.0 ...

Violation of change

Assuming you did not use anything in the application that was introduced in version 2.0, then there is a greater chance of backward compatibility.

What's New in 2.0

+1
source

The only problem I found in my code is the two controls in asp.net that are called the same with the other package. this was used to work in 1.1 but crash 2.0

This is a code menu, so there is no reason to cry about it.

+1
source

More articles:


All Articles