How to solve JavaScript IntelliSense problems in VS2010

re: How to solve JavaScript IntelliSense problems in VS2010

Earl.E.Brown — Mon, 22 Nov 2010 22:11:01 GMT

Thanks, Damian - that did the trick! And since our web-app is IE-only, I can just use the file-path syntax, and it's coverted by the browser...no asp tricks needed.

Thanks for the tip!

re: How to solve JavaScript IntelliSense problems in VS2010

Damian Edwards — Thu, 18 Nov 2010 05:21:12 GMT

theGleep@work - The issue in your case is you're using URL travesal syntax (forward slashes) to try and find a file path. If you change it to use backslashes IntelliSense will work, but you don't really want that to be rendered to the browser. You can get the "best" of both worlds doing something like this:

<% if(false) { %>

<% } else { %>

<% } %>

// IntelliSense for stuff in shared.js works fine here now

</script>

Hope this helps.

re: How to solve JavaScript IntelliSense problems in VS2010

Damian Edwards — Thu, 18 Nov 2010 02:34:06 GMT

theGleepWork - The issue with your exapmle is your trying to traverse a folder path using URL notation (forward slashes). If you change your src path to use back slashes, IntelliSense works. However this might cause you problems at runtime. You can get the "best" of both worlds by doing something like this:

<% if(false) { %>

<% } else { %>

<% } %>

// IntelliSense for stuff in shared.js works fine here now

</script>

re: How to solve JavaScript IntelliSense problems in VS2010

Earl.E.Brown — Wed, 17 Nov 2010 20:25:15 GMT

I have an odd setup (because I don't do things "normal") that's causing me to not have intellisense that I'd LOVE to have. I can work around it in .js files, but the <script...> tag in .html doesn't work right for me.

What works:

what doesn't work:

when editing "d:\Company\MyProjects\MyApp\MySite\MyPage.htm", using:

The *reason* this isn't working is because I actually have two projects ("existing web sites") in the solution:

the project "d:\Company\Scripts" manages scripts that are shared amongst multiple developers,

and "d:\Company\MyProjects" manages my personal collection of responsibilities.

So, the relative path from "D:\Company\MyProjects\MyApp\MySite" fails because the relative path traces to a folder before the projects "base folder"

I have a couple of options I'd like to see to allow fixing this, but I'm sure you all can come up with your own, as well:

* When in the editor, treat relative paths as relative *on the filesystem* instead of *in the project" (maybe make this a configuration option?)

* Allow [/// <reference path="d:\Company\Scripts\SharedScript.js"/>] within a <script> tag:

/// <reference path="d:\Company\Scripts\SharedScript.js"/>

var testIntellisense = external.fromShared.doSomething();

</script>

* Add a "reference" attribute to the <script src=""> tag:

* Add a configuration option for the javascript editor that pre-loads javascript files for intellisense

(I can see how this might cause other problems, though - like "what happens when the included script is the same as the pre-loaded script?" ... but I'm sure there are options to resolve that.)

OK...enough of me rambling. If anybody would like to get in touch with me, please e-mail! (I'll check back here to see if there's feedback here, as well.)

Thanksf or the patience to read all this!