21 Nov 2012 7:29 AM #11
Anyone have any luck with this?
I've tried everything mentioned in this thread and am getting flooded with:
messages followed by a timeout and sometimes an overflow.
This is my view:
<link rel="stylesheet" type="text/css" href="http://localhost/extjs/resources/css/ext-all.css" />
<link rel="stylesheet" type="text/css" href="http://localhost/extjs/examples/shared/example.css" />
/// <reference path="C:\inetpub\wwwroot\extjs\ext-all-dev.js" />
21 Nov 2012 3:18 PM #12
I know this doesn't solve your immediate issue, but thankfully 2012 is much better in this regard. It uses the Chakra engine which seems to do a much better job of understanding Ext. It's more robust all round.
That said, the reliance on object literals means there isn't actually that much autocomplete to provide. That is, until someone makes some TypeScript interface definitions
20 Dec 2012 5:59 AM #13
it works well
it works well
Ext4.1 & VS2010
add code below
///<reference path="ExtJS/ext-all-debug.js" />
then intellisense works
20 Dec 2012 2:38 PM #14
It does "work", but I'm not sure I'd say it works well in VS2010. Using your exact example with 4.1.0, the intellisense service starts falling over at about line 8,000. There is no autocomplete for anything defined after that point (which is the reason for this topic).
For example, type:
...and you'll get nothing (Ext.Msg isn't defined until line ~150,000).
On the other hand, if I use VS2012 and put ext-all-dev.js (highly recommended vs debug) in the new _references.js file, there is complete support for the whole library.
Not trying to be argumentative, but that's just the state of VS2010 with Ext JS.