Publish your extension to a local TFS Update 2 server
Turns out that the tools used to publish to the VSTS Marketplace work for the TFS one as well. to publish an extension you do need to pass in the service url manually and this took a little bit of fiddling to figure out what to put in there. Turns out that it takes the server root,
C:t>tfx extension publish --root . --manifest-globs vss-extension.json <br /> --service-url http://jessehouwing:8080/tfs --proxy https://xebia.com/blog:8888<br />Checking if this extension is already published<br />It isn't, create a new extension.<br />Waiting for server to validate extension package...<br /><br />=== Completed operation: publish extension ===<br /> - Packaging: C:tjessehouwing.jessehouwing-vsts-variable-tasks-0.0.0.vsix<br /> - Publishing: success<br /> - Sharing: not shared (use --share-with to share)<br />
If your server isn’t configured with Basic Authentication enabled, you can use the Fiddler hack to authenticate over NTLM. As you can see by the –proxy option int he command above, that’s what I’m doing at the moment.
It should be relatively easy to build a PowerShell script that uses the –json option to list all extensions on the local TFS Marketplace and then check the online marketplace for a newer version to automatically sync extensions which have already been installed. Stick that in a Build Definition on a Schedule and your local marketplace will always be up to date with the latest versions. That’s something for a future blogpost.