This publish command will publish the given runtime package to the directory that will ultimately be copied to the drop folder by the rest of the process

On this I step originally wasn’t paying attention to the dialog and put the entire command line in the “tool” text box. That won’t work and you’ll get an error claiming the tool executable can’t be found. That took a while to chase down in my case because a lot of the older posts/forums discuss how to get the dotnet tooling installed into a VSTS Build agent – but it is now built in (Its at C:\program files\dotnet”)

The final build process looks like this

After a build is performed the drop folder looks like thisI left in the original “Copy Files to” step in the build so that I had access to everything that was built as things progressed. But to run things I just need the folders under the “publish” directory

Log in to Ubuntu and download the publish directory

Last step is to run it

So the current overall workflow now is

Update the project on Windows in Visual Studio Community 2015

Check in to Github

VSTS automatically builds, runs unit test, and packages

Download to Windows or Ubuntu to run

Next I’m thinking “What could be better than running a 35 year old text adventure on Azure Service Fabric?”