Please let us know when this works, as per the channel9 video when the VS install directory is not drive C. (Boot [C] is a relatively small SSD, installs are in D, data is in E)
Mads, this looks like it would be great if it would work for me, but I've already spent a bunch of time dealing with the 'SP1 is required' issue, then seeing people reviewing about the problems with a typical, but apparently non-standard, installation location.
Since the video and hype is great, but the installation and usage has such issues, I've voted 3. It isn't crap or vaporware  and it isn't gold  (at least for me, get the installs fixed, then maybe).
Unfortunately, I had to uninstall this. After installing I could no longer edit CSS files in Visual Studio getting the same "unspecified error" that others are mentioning. Once I uninstalled, I could edit CSS files again.
Do NOT use this. After installing it, Visual Studio lost all ability to recognize CSS files, let alone have intellisense function. Uninstalling and trying to fix Visual Studio was a nightmare. Bad, bad, BAD extension.
When installed on a VS.NET SP1 that has the JScript Editor Extensions the backspace key stops working inside js code. Is there a way to make both tools work together?
JScript Editor Extensions: http://visualstudiogallery.msdn.microsoft.com/872d27ee-38c7-4a97-98dc-0d8a431cc2ed/
I mean, Installing "Update for the .NET Framework 4" didn't solve the problem, just give more specific information of my environment to the developer(
Mads Kristensen) for being helpful to correct the problem.
When installing this addin it states "Unable to installed because a newer verision of this product is already installed". I checked to see if "Web Tools\Web Standards Update for Visual Studio 2010 SP1\" existed in the "Program Files" directory, not found. VS2010 SP1 is installed and and the latest .net 4 framework patched have been applied.
For this HTML:
<img src='test.png' alt=''>
<p>This is valid HTML, but not valid XHTML!
Intellisense is still saying:
Validation (HTML5): Empty elements such as 'img' must end with />.
Validation (HTML5): Element 'p' is missing its closing tag.
However, the HTML5 spec states that empty elements do not have closing tags, and do not have to be self-closing. Similarly, <p> tags do not need closing tags in many situations.
It is bothersome that the editor is complaining about perfectly valid HTML5 markup.
We are aware of this issue, but unfortunately this might not be something that is easy to fix in the schema files alone. It might require a change to the running VS code that handles the HTML parsing and validation. We hope to get the fix for this in the next update.
After the update, my previously ok HTML5 validated documents in my mvc/razor project are suddenly saying Validation (HTML5): Element 'img' is not supported. Or 'div', 'a', 'iframe' and other content. Lovely.