Adding HTML5 Validation and Intellisense

Hi

I am trying to create an HTML5 web page in Visual Studio 2010 according to the information at the following link
http://blogs.msdn.com/b/cdnsoldevs/archive/2012/02/23/how-do-i-use-html5-in-visual-studio-2010.aspx
I followed the instructions below and changed it from  "XHTML 1.0 Transitional" to "HTML5". I have a number
of websites. Will this cause problems with my other projects? Is this a general setting that now governs all the sites I build?

You will definitely want to make sure you have Service Pack 1 installed! By installing Service Pack 1 you get both intellisense (can’t live without that anymore) and validation for HTML5. Don’t forget after you install Service pack 1 to go to Tools | Options | Text Editor | HTML | Validation and set the validation to HTML5 or XHTML5 or the HTML5 validation won’t work.
Murray BrownMicrosoft Cloud Azure/Excel Solution DeveloperAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

COBOLdinosaurCommented:
In general HTML5 is tolerant of XHTML, however XHTML may not recognize the new features and tags of HTML5.  As long as the doctype specifies XHTML or HTML, there should be no validation issues.  

Going forward XHTML has no future, There are no new versions in the pipeline.  It is a failed experiment that attempted to marry HTML and XML and it ended up with the worst features of both.  HTML5 on the other hand is a living standard that continues to have new feature implemented by browser manufacturers with each new browser release.  Even Microsoft, who have not been very supportive of web standards has committed to implementation of the HTML5 standards.

If you do find incompatibilities, I would recommend that your resolution of them should be to bring the older code up to the new standards rather than trying to find workarounds.

Cd&

Cd&
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Murray BrownMicrosoft Cloud Azure/Excel Solution DeveloperAuthor Commented:
Well written! Thanks for the advice. Much appreciated.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP.NET

From novice to tech pro — start learning today.

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.