VSTS Extension Project Templates

This extension contains a project template consisting of:

• A simple TypeScript app
• The required vss-extension.json file 
• A README containing links to further extensibility help 
• The VSS.SDK.js file needed to bring your VSO extension to life
• Several typings to help with referenced libraries (jQuery, Q, Knockout, VSS)
• An item template for a build/release task
• A project template for build/release tasks

Version 3.0 moves project template strucutres to align with the latest guidance from Microsoft.  Please visit https://github.com/Microsoft/vss-web-extension-sdk for more information on the latest extension guidance.

Version 2.5 addresses an issue with a new d.ts being included in the VSS.d.ts file.  Please see release notes for the full list of updates.

If you have any version prior to 2.0 installed, please uninstall and reinstall the extension.  Thank you!

Note: As of 1.7, there have been modifications made to the project that allow you to directly package the VSIX file for your extension. A gruntfile has been added to the project allowing for isolated running of the package and publish commands.  There is also now support for running Jasmine tests using Grunt.  The gruntfile looks to the settings.vset.json file, which is where you can set the name of your manifest, the output to look for when publishing, and your access token.

As of version 1.11, Application Insights support has been added.

If you run into any issues with the Task Runner Explorer complaining that you need to update your version of Node, go to Tools -> Options -> Projects and Solutions -> External Web Tools and move the line item for $(PATH) up to the top of the list.  As of this writing, the NodeJS tools ship with their own version of the Node executable (0.10.31).

As of 1.8, support for tasks in VS Code has been added.  Ctrl+Shift+B now runs the packaging task from the gruntfile.

As of 1.9, support for static content hosting is now supported, along with the use of the vss-sdk package via npm.  This ensures the typings and the VSS.SDK.js files are up to date on build.

Further information related to the creation of VSO extensions can be found in the README.md file, located in the sample project once the template is used.

Candid feedback welcome!