Problems upgarding to ASP.NET 2.0

Home ›

ASP.NET Forums » Migration to ASP.NET » Migrating from ASP.NET 1.x to ASP.NET 2.0 » Problems upgarding to ASP.NET 2.0

Shortcuts

Previous Next

Problems upgarding to ASP.NET 2.0

Last post 07-02-2009 12:42 PM by vpmragu. 11 replies.

Sort Posts:

Problems upgarding to ASP.NET 2.0

09-29-2005, 1:51 PM

Contact

10 point Member
SlaveOf1
Member since 09-29-2005, 5:37 PM
Posts 2

Hi all,
I tried to upgrade from ASP.NET pervious version to ASP.NET 2.0, but I got all these errors:

Error 2 Validation (XHTML 1.0 Transitional): Element 'html' is missing required attribute 'xmlns'.
Error 3 Validation (XHTML 1.0 Transitional): Empty elements such as 'meta' must end with />.
Error 4 Validation (XHTML 1.0 Transitional): Element 'script' is missing required attribute 'type'.
Error 6 Validation (XHTML 1.0 Transitional): Attribute 'height' is not a valid attribute of element 'table'.
Error 18 Validation (XHTML 1.0 Transitional): Element 'script' is missing required attribute 'type'.
Error 20 Validation (XHTML 1.0 Transitional): Empty elements such as 'img' must end with />.
Error 22 Validation (XHTML 1.0 Transitional): This name contains uppercase characters, which is not allowed.
Error 23 Validation (XHTML 1.0 Transitional): Empty elements such as 'IMG' must end with />.
Error 24 Validation (XHTML 1.0 Transitional): This name contains uppercase characters, which is not allowed.
Error 25 Validation (XHTML 1.0 Transitional): Element 'html' is missing required attribute 'xmlns'.
Error 26 Validation (XHTML 1.0 Transitional): This name contains uppercase characters, which is not allowed.
Error 27 Validation (XHTML 1.0 Transitional): This name contains uppercase characters, which is not allowed.
Error 28 Validation (XHTML 1.0 Transitional): This name contains uppercase characters, which is not allowed.
Error 29 Validation (XHTML 1.0 Transitional): This name contains uppercase characters, which is not allowed.
Error 30 Validation (XHTML 1.0 Transitional): This name contains uppercase characters, which is not allowed.
Error 31 Validation (XHTML 1.0 Transitional): Empty elements such as 'META' must end with />.
Error 36 Validation (XHTML 1.0 Transitional): This name contains uppercase characters, which is not allowed.
Error 39 Validation (XHTML 1.0 Transitional): This attribute name must be followed by an equal (=) sign and a value. If the value is in quotation marks, the quotation marks must match.
Error 43 Validation (XHTML 1.0 Transitional): Empty elements such as 'br' must end with />.
Error 44 Validation (XHTML 1.0 Transitional): Empty elements such as 'br' must end with />.
Error 47 Validation (XHTML 1.0 Transitional): This name contains uppercase characters, which is not allowed.
Error 48 Validation (XHTML 1.0 Transitional): Empty elements such as 'br' must end with />.
Error 49 Validation (XHTML 1.0 Transitional): Empty elements such as 'br' must end with />.
......

I got hundreds of errors and warnings.

Do I have to go and change manually all the aspx and html pages?? there will be hundreds of changes!!
Also the upgarde create a new code then there an error in the code that he created?(App_Web_bojdxrs-.4.cs 213 ) what is all these codes that has been created in temprory folder? C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\

Any idea?

Abdu.

Re: Problems upgarding to ASP.NET 2.0

09-30-2005, 11:07 AM

Contact

145 point Member
gerrod
Member since 04-21-2005, 3:05 PM
New York
Posts 29

In v2, Microsoft have gone with XHTML 1.0 Transitional as the default doctype on pages. In v1.1, the default doctype was HTML 4.0 Transitional.

As you've no-doubt guessed, you're now working with a much more strict standard. So you have 2 options:

Change all your HTML as the warnings suggest. This will make your pages XHTML compatible - which is a good thing.
Go back to HTML 4.0 Transitional. You can do this by changing the doctype declaration at the top of your pages as follows:

You can also read more about doctypes at the w3 schools site.

Regarding the temporary code, this is part of the "on-the-fly" compiling of the v2 framework. If you find that you're getting errors in there, sometimes it helps to manually delete all the files in that temporary directory. You'll be best to run IISRESET before you do that, though.

HTH -
/gerrod

Re: Problems upgarding to ASP.NET 2.0

09-30-2005, 5:12 PM

Contact

10 point Member
SlaveOf1
Member since 09-29-2005, 5:37 PM
Posts 2

Thanks for your reply!

I changed the pages headers to support HTML 4.0 Transitional.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" >

But u'm still getting the same errors:
Validation (XHTML 1.0 Transitional): Element 'html' is missing required attribute 'xmlns'..

Any idea?

Thanks.
Abdu.

Re: Problems upgarding to ASP.NET 2.0

10-12-2005, 10:57 AM

Contact

10 point Member
kazzmeister
Member since 10-11-2005, 4:49 PM
Posts 2

The quickest way to get rid of the build errors is to turn off validation, which is on by default. In Visual Studio 2005, with your project open if you only want to affect one project, go to menu option Tools then Options. In the Options dialog navigate to Text Editor, HTML, Validation. Uncheck the Show Errors option for your target browser. Build again and you won't see the validation errors. Cool [H]

Re: Problems upgarding to ASP.NET 2.0

12-07-2005, 2:28 PM

Contact

15 point Member
bloomk
Member since 09-12-2002, 8:13 PM
Posts 3

kazzmeister wrote:
The quickest way to get rid of the build errors is to turn off validation, which is on by default. In Visual Studio 2005, with your project open if you only want to affect one project, go to menu option Tools then Options. In the Options dialog navigate to Text Editor, HTML, Validation. Uncheck the Show Errors option for your target browser. Build again and you won't see the validation errors.[H]

awesome! i needed that... thanks...

Re: Problems upgarding to ASP.NET 2.0

12-16-2005, 5:34 PM

Contact

1,536 point Participant
ClayCo
Member since 06-14-2002, 10:11 AM
United States
Posts 291

Hello Abdu,

The Visual Web Developer designer doesn't directly use the <!DOCTYPE ... > element at the top of the page for design-time validation -- that's just the way you advertise which language the page was written in to the browsers/search bots/etc. that request the page. The validation target used for the validation errors you asked about is actually found in a dropdown in the "HTML Source Editing" toolbar that should be visible by default when editing an ASPX page in Source View. You could turn validation off entirely, but you generally should pay attention to these errors since they make it harder to machine-parse your content.

HTH,
Clay

Re: Problems upgarding to ASP.NET 2.0

02-13-2006, 2:54 PM

Contact

202 point Member
Supergibbs
Member since 02-13-2006, 7:51 PM
Santa Barbara
Posts 47

Pressing Ctrl K, D (hold control and press k then d) will fix many of these errors. The rest are fairly easy to change. It does take some time, but I applaude MS for trying to push the newer XHTML standards.

and search and replace for <br> to <br /> helps a lot too

-Jesse

Re: Problems upgarding to ASP.NET 2.0

02-22-2006, 10:07 AM

Contact

74 point Member
lonechicken
Member since 09-25-2002, 9:06 AM
Posts 20

In general, I find the strict validation useful, but is there a way to customize what gets (or more importantly: doesn't get) flagged? Not something general like, "when client tags are not lowercase" inside tools->options but something specific...

The web stats package I use needs a non-standard attribute stats="1" added inside the <body> tag for any page I need kept track. So for the hundreds of pages on the site, this validation error spams the error list: Attribute 'stats' is not a valid attribute of the element 'body'.

How do I configure VS or at least the project to ignore this (and other) specific "errors" so I don't have to turn off the error list entirely?

Re: Problems upgarding to ASP.NET 2.0

04-24-2007, 12:06 PM

Contact

4 point Member
lokanatha
Member since 04-23-2007, 8:50 AM
Banglaore
Posts 3

Hi Friend,

Instead you can add

html xmlns="http://www.w3.org/1999/xhtml">

which almost eliminates your problem. bcoz i did this way only i got out of the problem.

Lokanatha Reddy Palle

Re: Problems upgarding to ASP.NET 2.0

10-16-2008, 2:53 PM

Contact

2 point Member
bindubn
Member since 09-26-2008, 10:25 PM
Posts 2

Thanks. It really solved the error.

Re: Problems upgarding to ASP.NET 2.0

10-24-2008, 5:20 AM

Contact

20 point Member
ssudar
Member since 09-29-2008, 8:56 AM
Posts 22

Thanks,

<html xmlns="http://www.w3.org/1999/xhtml">

This really solvs HTML problem.

Thanks a lot,

Regards,

Shahaji Udar

Thanks and Regards,

Shahaji Udar.
MCTS,
Pune,INDIA.

Re: Problems upgarding to ASP.NET 2.0

07-02-2009, 12:42 PM

Contact

81 point Member
vpmragu
Member since 01-09-2008, 1:43 AM
Bangalore
Posts 28

hi,

i try to convert my webapplication project from .net 1.1 to .net 3.5.

All are ok.

but some XSD file in my project.

when i try to build my application, it throws warning like,

"Errors occurred while compiling the Xml schemas in the project. Because of this, Xml intellisense is not available"

how to resolve my problem?

Thanks in Advance.

RaguNathan Maniraj,
Software Engineer,
Bangalore.

Page 1 of 1 (12 items)

RSS Available