Pretty sure this won't work on server

[jessehouwing]

And 4-part version numbers aren't really used on the marketplace, the fact they work is an undocumented bonus features.

[rajbos]

Thanks! GHAzDo is not supported on server, so that is not needed indeed. Documentation states the current value is correct though: link:

• Microsoft.VisualStudio.Services (extensions that works with Azure DevOps or TFS),
• Microsoft.TeamFoundation.Server (extension that works with TFS),
• Microsoft.VisualStudio.Services.Integration (integrations that works with Azure DevOps or TFS),
• Microsoft.TeamFoundation.Server.Integration (integrations that work with TFS)

[rajbos]

Ah, darn it, I happened to scroll down and there it states:

• Microsoft.VisualStudio.Services.Cloud: installs into Azure DevOps Services
• Microsoft.TeamFoundation.Server: installs into TFS
• Microsoft.VisualStudio.Services: installs into both. Shortcut for Microsoft.VisualStudio.Services.Cloud and Microsoft.TeamFoundation.Server version [14.2,)

[rajbos]

I'll add the targets fix in another branch with #14. Do you have any idea how well Azure DevOps would handle the version schema update if I go from 4 to 3 numbers? Does it understand it is an upgrade then?

[jessehouwing]

As long as it's a higher version it won't care.

[rajbos]

Handled comments, closing the issue. Thanks again!