JavaScript intellisense does not work on classes within namespaces - by Morten_Nielsen

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 301947 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 10/1/2007 2:14:49 PM
Access Restriction Public

Description

When creating  a class within a namespace, no intellisense support apart from the default Object properties is given for the class instance, or for the individual "levels" in the namespaces.
Sign in to post a comment.
Posted by Microsoft on 9/4/2008 at 6:48 PM
Hi MNielsen,

We hear your feedback. That coding pattern *is* the right pattern to promote from a developers standpoint. Unfortunately it's not simple to have IntelliSense accomodate that pattern. We will be working to advance IntelliSense to a point where it can understand such patterns in a future release.

Thanks!
The Web Tools Team
Posted by Morten_Nielsen on 10/5/2007 at 10:21 AM
Type.registerNamespace() is the pattern you have been promoting all along, and not supporting it is just not acceptable.

You don't support namespaced objects and you don't support scripts embedded by webcontrols, so what is that I'm really getting from the JScript Intellisense ?!?
I can live without the default 7-8 properties on all object types. I know those already, and thats not the ones I need intellisense on.

This is probably the most hyped feature of VS2008, but in the end it's more or less useless.
Posted by Microsoft on 10/4/2007 at 4:15 PM
Hi MNielsen,

The parser that analyzes the active document doesn't realize that the registerNamespace() function actually has the side effect of creating an object called 'Test'. It's really difficult to write logic that can infer that. Thus the IntelliSense doesn't work quite right in that situation. This work in external docs because we virtually execute the code to get around this. We hope to come up with a solution to this next version.

Thanks for your feedback!
The Web Tools Team
Posted by Microsoft on 10/1/2007 at 11:48 PM
Thanks for your feedback.

We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team
Posted by Microsoft on 10/1/2007 at 11:35 PM
Thank you for your feedback. We are currently investigating. The investigation process normally takes 7-14 days. If this issue is urgent, please contact support directly (see http://support.microsoft.com).

If at any time your issue is closed unsatisfactorily, you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team