Pitfalls for converting a .net 1.1 solution to .net 2.0

Question

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 fully backwards compatible with 1.1?

Answer 1

I think its depends on your code, the best option is to perform a trial run and see what errors it will generate. I dont think .NET 2.0 is fully backwards compatible, though they claim it is.

Common conversion issues and solutions

1.1 to 2.0 compatibility