Is there a reason for testing applications when converting from 2.0 to 3.5.

Some people say that 3.5 is on top of 2.0 so when converting an application there is no need to test.
The application will run identically. Is this true? I need concrete proof.

Who is Participating?
techExtremeConnect With a Mentor Commented:
Regardless of what is said, you must always test thoroughly your application if you are doing some major change like moving your application from one .net framework to another.
You never know , if you are new that if some methods / properties that your application is using are no longer available or obsolete in the new framework, there is something bigger and better out there which if replaced in your code can have major performance improvements and stuff like that.
I would certainly not assume my application to be running successfully without testing in the new framework (especially when it was not built for the same!)
Actually there is reason.
I had the opportunity to experience that myself. I converted a small appl from 2.0 to 3.5.
Conversion happened seamlessly.
However there was one page that was working before that went rogue on me. I used Request.ApplicationPath to help build some links dynamically. I was working fine in 2.0, not anymore in 3.5. I had to do a quick work around.

If you have time a resource, test. If you dont, try.
See another example of what I was talking about :)
mathieu_cuprykAuthor Commented:
great answer tech.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.