Dotnet Test Now publishes test results Dotnet Test command issue I am using VSTS for both hosting my code and building/deploying stuff. Amongst them I have a couple of .net core build pipelines, and I am using the
markdown Moved to Ghost blog engine I recently fell in love with writing everything in markdown, so I looked for a blog engine that would support this new habit. Ghost was the one, and a combination of Docker and
Build and deployment of ASP.NET Core 1.0 to Azure App Service Intro Now that the .net Core bits are RTM I wanted to start playing with a new website to get the feel for the new toolchain and the development/deployment lifecycle around .net
New build agent image with dotnet sdk 1.0.0-preview2-003121 released The VSTS team announced updated versions of the hosted build agents, to now support the current dotnet 1.0 tooling (1.0.0-preview2-003121). No more need for a private build agent for the
XUnit and .NET Core not showing the little unit test “Run shortcut” in Visual Studio 2017 I have battled with this for a few days, and if you google around, there is plenty of issues with XUnit tests not showing up in the test explorer. But mine does. Just
Blogengine.Net and posting from Windows Live Writer to a HTTPS site I don’t know if this is specific to my setup, but after deploying Let’s Encrypt certificates to my Azure App Service hosted site, I had a problem with Windows Live Writer