Your official information source from the .NET Web Development and Tools group at Microsoft.
Ext is great framework for adding rich AJAX interactivity to your web application. Unfortunately, JScript IntelliSense currently has difficulties processing the script and it's not uncommon to see this message:
I just wanted to let everyone know that we've investigated and fixed the issue. This fix will be available in the next service pack (no date announced yet). In the meanwhile, there's actually a simple workaround. In a file that runs before ext-base.js, or on the first-line of ext-base.js itself, add the following code:
window.addEventListener = false;
This corrects for an inaccuracy in our simulated execution environment. Once again, after the next service pack, this workaround will no longer be neccesary. I quickly experimented with Ext 2.0.2...
...and Ext 1.1.1...
Ext is one of the larger libraries out there and thus it takes longer to execute. If you've been seeing...
...increasing the timeout will often solve the problem.
Increasing the Timeout
By default, every IntelliSense request is only allowed 15s to execute. This is to prevent IntelliSense from scripts with infinite loops. If you have a large script or slower machine, it may make sense to increase the timeout limit. The timeout value store within following registry keys (depending on if your are using Express or the full product). The value is in milliseconds so choose something greater than 15000.
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\HTML Editor\JsFailsafeTimeout HKEY_CURRENT_USER\Software\Microsoft\VWDExpress\9.0\HTML Editor\JsFailsafeTimeout
On a related note, we've read all the requests for Prototype support. Like Ext, We've fixed the issue for the next service pack. But unlike Ext, there isn't a temporary workaround to be offered. We hope this info unblocks your work. Thanks for using our editor!
Jeff King Program Manager Visual Studio Web Tools
This also seems to only work when using the Ext-base and not one of the adapters such as JQuery.
Great work though - it was like christmas had come - seeing that 'Ext' popup in my intellisense!!!
@Wayne: Out of curiosity, are you using Ext1 or Ext2?
Hey geoffrey, thanks for your feedback as well..
I have use all reccomendations given here. But I have such error.
Error updating JScript IntelliSense: Client-side script IntelliSense information was not generated due to an error in an external script reference.
I tested with ExtJs 2.0.2 and ExtJs 2.1. Everywhere is same error.
I have used all reccomendations given here. But I have such error.
@beckenov: Could you provide me with a sample of the project you are experiencing the error with? My email is (jking-at-microsoft-dot-com). Thanks!
I have the same problem as beckenov.
If I download the latest ExtJS 2.1 and create a new site. Then add a Extjs folder and copy in the ExtJS files and then add a new js file and add the following:
/// <reference Path="../Extjs/adapter/ext/ext-base.js"/>
/// <reference path="../Extjs/ext-all-debug.js"/>
If I remove ext-all-debug.js then no error (same error with ext-all.js)
Problem was caused by having the <reference name="MicrosoftAjax.js"/> reference in. So no debugging both!!
Visual Studio 2008 SP1 Beta is now available! You can download it here . In SP1, we have added some new
@Richard: I'm able to use MicrosoftAjax.js + ext-base.js + ext-all-debug.js and IntelliSense is working. I realize I'm on a VS2008 SP1 Beta build (so I don't need the shim). If you plan on trying out the beta, let me know if it fixes it for you. If you don't plan on trying the beta, let me know and we can further diagnose. Thanks!
I just installed SP1 beta, no extjs intellisense.
with the shim, intellisense works, but when I remove it I get the following error
Error updating JScript IntelliSense: C:\Users\EShy\Documents\Visual Studio 2008\Projects\ExtJS2\ExtJS2\Ext\adapter\ext\ext-base.js: Object doesn't support this property or method @ 9:7311
C:\Users\EShy\Documents\Visual Studio 2008\Projects\ExtJS2\ExtJS2\js\application.js 1 1 ExtJS2
this is with Ext 2.1 (using the VS2008 project template from the extjs forums)
what could be the problem?