Intellisense
There are 7 entries for the tag
Intellisense
UPDATE: be sure to see official response at the end of this post.
As Joel D'Souza and I were discussing VS10 JavaScript Intellisense it became clear that, while it is overall an improvement from 2008, there is one silly bug.
MS Connect Bug: https://connect.microsoft.com/VisualStudio/feedback/details/553372/vs10-javascript-intellisense-class-member-decorator-display-depends-on-microsoftajax-js
In exploring javascript intellisense in VS10, it came to my notice that enums, interfaces and namespaces and classes all are decorated properly by adding the proper tag properties, but the class member decorators, e.g. events and properties etc, fail to display unless MicrosoftAjax.js was referenced.
The line in MicrosoftAjax.js that 'triggered' the proper display of class member decorators is:
Object.__class = true;
Surely...
// an empty object with xmldocs for assistance in creating ajax settings
var ajaxSettings = function() {
/// <summary>A set of key/value pairs that configure the Ajax request. All options are optional.
/// A default can be set for any option with $.ajaxSetup().</summary>
/// <field name="async" type="Boolean">Default: true
/// By default, all requests are sent asynchronous (i.e. this is set to true by default). If you
/// need synchronous requests, set this option to false. Note that synchronous requests may temporarily
/// lock...
Or: “What I hope is not just ‘Yet Another Visual Studio JavaScript Intellisense Walkthrough’”.
Author note: If this content seems dated, it is. When I started this blog last year I began by resurrecting a monster javascript documentation project that had been dormant for a year. Then I got busy and dropped it again. So here I am picking it back up again to provide some motivation for actually finishing a POJO documentation generator using xml doc comments and SCHB. While VS JScript Intellisense is nothing new I think that there are topics covered that I have not seen in other...
I have forked JsUnitTest over at github into JsUnitTest-VS in the interest of creating a Visual Studio 2008 friendly JavaScript unit testing framework.
The fork, new name and versioning are prompted by the fact that the infrastructure of the project is php/ruby oriented. I am not only NOT really inclined to switch my development paradigm to PHP/RUBY to work on a library that is intended for Visual Studio, I have identified various areas in which I intend to make fairly significant changes to the feature set. Reconciliation can be considered at a later date.
That said, I intend to maintain full API compatibility to keep...
download source code
download this article in .doc format.
Overview
In a recent article I presented a simple implementation of a generic type system in JavaScript. Please see that document for a detailed enumeration of the motivations and benefits, including type safetly and Visual Studio intellisense support.
In this document I will present a 'better' implementation that eliminates many of the limitations of my 'simple' generic type implementation.
I will also provide a starter library of generic compatible collections including Queue, ListArray and Dictionary that you may use immediately and that can serve as a reference for implementing your own generic types in JavaScript.
Features:
...
source and demo
What are 'generic types'?
A generic type is defined using one or more type variables and has one or more methods that use a type variable as a placeholder for an argument or return type. For example, the type java.util.List<E> is a generic type: a list that holds elements of some type represented by the placeholder E. This type has a method named add(), declared to take an argument of type E, and a method named get(), declared to return a value of type E. source
Why attempt this in JavaScript?
My answer is two-fold. Primarily for type safety. While the...
visual studio javascript intellisense friendly
// enum creation pattern
// NOTE: i am not doing the intensive argument validation
// and restricting the enum values to integer as is done in
// msajax so you can probably break this with little effort.
function createEnum(type, flags)
{
for (var i in type.prototype)
{
type[i] = type.prototype[i];
}
// __xxx props are msajax/vs talking to each other
type.__enum = true;
type.__flags = flags;
}
intEnum = function()
{
/// <summary>
...