while migrating asp.net 2.0 to asp.net 3.5 is any issues will raise

Question

0.00/5 (No votes)

See more:

in of my current app was developed by asp.net 2.0while migrating asp.net 2.0 to asp.net 3.5 is any issues were not raise,

i said this to someone ,but those are not belies me.

with out any errors we can do it?

Posted 30-May-12 9:05am

jameschowdaree

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2012-05-30T09:23:00

Yes.

It is possible to change from .NET V2.0 to .NET 3.5 without any errors being found, or needing any changes to your code.
You may get error or warning messages when you upgrade, it depends on the classes and the properties / methods of those classes you used in the original V2.0 application - some are depreciated in V3.5 and you get told about that. But in general, you can upgrade without any changes needed.

You can't necessarily go the other way though! :laugh:

Tim Corey · Accepted Answer · 2012-05-30T09:21:00

You will need to test this move. We have done it with minor issues. The biggest issue we faced was the web.config files, which all reference the 2.0 dlls and assemblies. You will need to modify these by hand, I believe.

Beyond this, it will depend on what your dependencies are. It could be a smooth upgrade or you could break everything. The absolute best advice I can give is to test it thoroughly before you take the changes live (and make sure you have a backup).

while migrating asp.net 2.0 to asp.net 3.5 is any issues will raise

2 solutions

Solution 2

Solution 1

Add your solution here

Preview 0