Welcome to MSDN Blogs Sign in | Join | Help

Visual Web Developer Team Blog

Your official information source from the Visual Web Developer team.

News

  • These postings are provided "AS IS" with no warranties, and confer no rights. Use of included code samples are subject to the terms specified Terms of Use
Visual Studio 2010 Beta 2 – Intellisense Issue in Javascript/HTML.

If by any chance you are not seeing intellisense in your JavaScript or HTML after installing Visual Studio 2010 Beta 2 you might be running into a known bug that we can show you how to fix.

The bug is related to user settings which we don’t remove when Beta 1 is uninstalled. One particular setting under HKCU\Software\Microsoft\VisualStudio\10.0\HTML Editor\TargetFriendlyName. For Beta 2, this setting does not match the schema’s we know about. As a result, JScript intellisense will fail to load and most items will be missing in markup as well.

The minimum fix is to manually repair the TargetFriendlyName setting in the registry (change it to be just "XHTML 1.0 Transitional”) but due to the fact that more settings could be affected the recommended fix is to reset all settings after Beta 2 is installed.

To reset all settings drop down the Tools menu and select Import and Export Settings. This will bring up the Import and Export Settings Wizard as seen below. Choose the last option “Reset all settings” and click Next when ready.

image

From there choose whether you want to saving your settings or not and click Next again.

image

Finally, choose the collection of settings that best fits your development environment and click Finish when done.

image

Thank you,

Mike Snow
SDET Lead 
Visual Studio Web Tools

Posted: Friday, October 23, 2009 1:39 PM by WebDevTools

Comments

WebDevTools said:

We discovered this is an issue with VS2009SP1 to VS2010 Beta2 installation as well.  Problems you might see are:

- JScript intellisense not working

- HTML intellisense is not correct

- validation error in source view

To fix the problem, in addition to above workaround, manually setting schema name in Tools.Options.Text Editor.HTML.Validation page should do it.

Masako

# October 23, 2009 7:30 PM

Jack said:

just hope the intelligence will work fine

# October 25, 2009 7:14 PM

Aaron said:

That tip definitely helped me resolve this problem!

# November 9, 2009 5:34 PM

Simon said:

Great tip - thank you. Worked for me as well.

# November 20, 2009 8:59 AM
Leave a Comment

(required) 

(required) 

(optional)

(required) 

  
Enter Code Here: Required

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Page view tracker