Problem when converting webapp 2008 to 2010

Question

0.00/5 (No votes)

See more:

.NET3.5

VS2008

, +

I have been developing a webapp with VS2008 with .NET 3.5 and I moved to VS2010 and .NET 4.0.
I moved the solution folder to my new computer with VS2010 and I began the process of converting it to .NET 4.
After this everything appears to work fine, but now when I make redirect to any page I get a HTTP Error 400 - Bad Request.

Thanks all

Posted 1-Jun-11 0:25am

mohammed sadeq

Updated 1-Jun-11 0:44am

Rob Branaghan

v2

Add a Solution

1 solution

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2011-06-01T07:37:00

I should not be related to the conversion itself: Framework 4.0 is backward-compatible with 3.5. It looks like your solution itself has bugs which makes it not movable (hard-coded path strings could be one reason). Do one step at a time. Make moved site working without conversion to 4.0, and them convert. Alternatively, convert your solution first on the same location and make sure it works first.

One more advice: clean up the solution from any artifacts except pure source code. You need to know exactly which files belong to the source code. Always work under some revision control system. Move solution not manually, but by wiping your local directory and checking out the code to a different location. Try to move solution around on the same computer first, to make sure you're not missing something.

At lest, you won't blame the innocent Visual Studio conversion procedure.

—SA