Problems arrising after web site conversion.

Question

0.00/5 (No votes)

See more:

I converted a Visual Studio 2008 web site to a Visual Studio 2010 web site. Usually all .cs, .aspx and .designer.cs files were grouped together in the Solution Explorer. After the conversion the .designer.cs files are separately listed in the Solution Explorer. Why is this? Is there a way to fix it?

With my newly converted web site, the code behind of every page gives errors. The errors that I get are all the same and they state the following:
"'type' does not contain a definition for 'member' and no extension method 'name' accepting a first argument of type 'type' could be found (are you missing a using directive or an assembly reference?)." I strongly suspect that this error is related to what I explained above. Strangely, when I build the project it builds successfully, but after a while it shows those same errors again at design time. Any help on this?

Posted 14-Sep-10 22:38pm

Hardus Lombaard

Add a Solution

Comments

Dalek Dave 15-Sep-10 4:40am

Do not try to work out the logic of MS, it defeats the greatest of minds! :)

Hardus Lombaard 15-Sep-10 4:45am

So you suggest that I should just continue with my work and ignore all this? I'm afraid that I might get problems in the future.

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)

Hardus Lombaard · Answer 1 · 2010-09-15T01:56:00

Solution 1

I think I figured out a solution to my problem. All I did was to delete all the .aspx.designer.cs files. Now I have no errors and the project builds successfully. :-D

Posted 15-Sep-10 1:56am

Hardus Lombaard

Comments

Hardus Lombaard 15-Sep-10 8:07am

Nope I was wrong - I still have all the errors, but the project builds successfully. This is very strange. Visual Studio reports 0 errors after a successful build, but then after a while and some activity it again reports the same errors. Don't know why. :(

aayu 15-Sep-10 8:13am

well i think you should rename all because you have convert the file so it is not supporting try using it may it work....

Hardus Lombaard · Answer 2 · 2010-09-15T04:25:00

Solution 2

Ok I got the solution, but it's not a quick one. Every page basically has to be redone. I created a new page for every one, just copied the code over and deleted the old pages. There - problem solved, but it took a while. :)

Posted 15-Sep-10 4:25am

Hardus Lombaard

Comments

LloydA111 15-Sep-10 12:50pm

When I used to use VS, I never bothered trying to use the conversion wizard to upgrade code to a newer version of VS, I just did what you did, copy the code manually!