Issues with upgrading a site from .net 2.0 to 3.5

Question

I want to upgrade my company website from 2.0 to 3.5. I think it should be fairly painless as all the old methods are still supported (just depreciated) in newer versions of .net. Is that correct?

Answer 1

We had no issues at all upgrading all of our apps from 2.0 to 3.5

I doubt you'll have any issues because .NET 3.0 and 3.5 are "additive" releases - meaning the core functionality of .NET 2.0 remains the same, these just add features.

This brief article explains it a little more clearly: https://web.archive.org/web/20211020133927/https://www.4guysfromrolla.com/articles/112107-1.aspx

As a side note, we also had no problems going from 2.0 straight to 4.0. Microsoft has been doing a pretty good job of keeping the upgrades painless.

I would like to throw in a caveat - if you're using third party components, I can't vouch for how easily they survive the upgrade process, but given the additive nature of the releases through 3.5 I think you'll be fine.