What are extensions?
This section covers developing custom extensions and service-hooks, to find information on installing extensions from the Marketplace, or buying Visual Studio Subscriptions, visit the Marketplace documentation.
What makes up an extension?
- A JSON manifest file contains basic info about the extension.
- Discovery assets - the markdown and images that make up your extension's overview and aesthetics in the marketplace.
- Static files that contain the logic of your extension, including HTML, JS, and CSS files. Static files are only applicable to contribution-based extensions.
All of these are bundled up to make a Team Extensions Service Package (.vsix file) that is published to the marketplace. From the marketplace, extensions can be installed directly by Azure DevOps Services users.
What can you do with extensions?
There are dozens of places where you can add to the Azure DevOps Services user interface, and we're adding more every sprint. Learn about all of the places where you can add a hub in the contributions reference.
- Provide new Azure Pipelines tasks that teams can use in their builds.
- Use dashboard widgets to get custom views within Azure DevOps Services.
- Extend the work item form with new tabs, sections, and actions.
- Create your own hub to embed new capabilities within our Agile, code, build, and test experiences.
- Develop actions that can be run on hubs, whether they're ours or ones you've created.
Extension building checklist
- Familiarize yourself with an overview of our platform and what's possible with it
- Learn to build your first extension or check out our full set samples
- Familiarize yourself with our RESTful APIs. If you're integrating from a 3rd party app or service, you'll also want to check out our Service Hooks
- Once your extension is ready, you'll want to package it up, publish it to the Marketplace, and we hope you'll share it with the community!
Send feedback about: