Skip to main content

One post tagged with "azure devops marketplace"

View All Tags

Visual Studio Marketplace: images in Markdown!

ยท 3 min read

I've recently found myself developing custom pipelines task extensions for Azure DevOps. The extensions being developed end up in the Azure DevOps Marketplace. What you see there when you look at existing extensions is some pretty lovely documentation.

screenshot of a rich Markdown powered screen with images in Visual Studio Marketplace

How can our tasks look as lovely?#

That, my friends, is the question to answer. Good documentation is key to success. Here's the ask: when a custom task is installed it becomes available in the marketplace, we want it to:

  • contain documentation
  • that documentation should support images... For a picture, famously, speaks a thousand words

Mark(Down) our manifest#

To get documentation showing up in the marketplace, we need to take a look at the vss-extension.json file which lies at the root of our extension folder. It's a kind of manifest file and is documented here.

Tucked away in the docs, you'll find mention of a content property and the words:

Dictionary of content files that describe your extension to users... Each file is assumed to be in GitHub Flavored Markdown format. The path of each item is the path to the markdown file in the extension. Valid keys: details.

This means we can have a Markdown file in our repo which documents our task. To stay consistent with most projects, a solid choice is to use the that sits in the root of the project to this end.

So the simple addition of this:

{    //...    "content": {        "details": {            "path": ""        }    },    //...}

Gives us documentation in the marketplace. Yay!

Now the images...#

If we are referencing images in our then, as it stands right now, they won't show up in the marketplace. It'll be broken link city. Imagine some Markdown like this:

![alt text](images/screenshot.png)

This is entirely correct and supported, but won't work by default. This is because these images need to be specified in the files property of the vss-extension.json.

{    //...    "content": {        "details": {            "path": ""        }    },    "files": [        {            "path": "images",            "addressable": true        }    ]    //...}

Consider the above; the path of images includes everything inside the images folder in the task. However, it's crucial that the "addressable": true is present as well. It's this that makes the files in this path URL-addressable. And without that, the images won't be displayed.

That's it! We're done! We can have rich, image inclusive, documentation in our custom tasks.

A final note: it's possible to specify individual files rather than whole paths in the files directory and you might want to do that if you're being very careful around file size. There is a maximum size for a custom task and it's easy to breach it. But by and large I find that "allowlisting" a single directory is easier.