Your official information source from the .NET Web Development and Tools group at Microsoft.
The issue is caused by the Jscript engine not being registered properly during the installation of Visual Studio. There is an easy workaround for this installation issue that will restore full functionality of Jscript IntelliSense.
To fix the problem, you will need to modify two registry values. Please be extremely careful when working with your system registry. If you are not familiar with Windows Registry and regedit tool, please ask your computer administrator to fix the issue for you.
The registry values you need to modify are
"CodeBase"=file:///C:\\Program Files\\Microsoft Visual Studio 9.0\\Common7\\IDE\\Microsoft.JScript.AuthoringServices.dll
Instead of the values you see above, you very likely have values “file:///” for both of the above registry entries if you are experiencing this issue. You need to replace those values with full path to Microsoft.JScript.AuthoringServices.dll library that is installed in the Common7\IDE subdirectory of your Visual Studio installation. In the examples above, Visual Studio was installed to “C:\Program Files\Microsoft Visual Studio 9.0”, so the correct values for the registry entries were “file:///C:\\Program Files\\Microsoft Visual Studio 9.0\\Common7\\IDE\\Microsoft.JScript.AuthoringServices.dll”
The following two images show the incorrect registry content. Note the circled values and registry key names:
The corrected values should look like the following:
After making these changes, full functionality of the Jscript editing in Visual Studio should be restored. Please let us know if you experience any further problems!
- Alex GavrilovSoftware Development EngineerWeb Development Tools
This posting is provided "AS IS" with no warranties, and confers no rights.
【原文地址】 Fixes for Common VS 2008 and .NET 3.5 Beta2 Issues 【原文发表日期】 Saturday, August 04, 2007 12:10 PM
We did discover another issue when the entire Microsoft.JScript.AuthoringServices.dll file is missing. We see this happen if Silverlight Beta 1 is uninstalled after Visual Studio 2008 Beta 2 is installed. The easiest way to repaire the problem is to re-run Visual Studio 2008 setup and choose the "Repair" option. That should place the file back into its intended location.
Thanks Alan, it was actually an error in an Ext file.
But alas, no intellisense for Ext, VS can't handle the way Ext is programmed...
Ok, in no particular order, here are 5 features in VS 2008 which are going to save me some time: Extender
It has been a little over a week since we released Beta 2 of VS 2008 and .NET 3.5 . So far the feedback
Thanks a million for this, worked a charm
Stötte på patrull när jag installerade Team Explorer till Visual Studio från en TFS 2008 Beta II-image:
Stötte på patrull när jag installerade Team Explorer till Visual Studio från en TFS 2008 Beta II-image