17 years after RFC 2818 deprecated the use of the commonName attribute in an SSL certificate as a means of identifying the domain name for which it’s valid, Chrome 58 has enforced it.
Our first hint at this was when a colleague found his development environment suddenly broken. Chrome was reporting “Your connection is not private” when connecting to IIS Express.
The security tab in the developer tools gave the next clue with an error stating “Subject Alternative Name Missing”.
Fixing it, however, took a bit of digging. I would hope there’s an easier way to fix this, but I threw together this Powershell script that seems to do the job (run as Administrator).
Visual Studio Online has built in support for Slack web hooks so that various events can trigger a message to a Slack channel. These events include things like code check in or build completion, but do not have any triggers for Release Management. As a work around, we hooked up our release definition manually and this post shows how.
Microsoft has documented the process for building and deploying ASP.Net 5 applications to Azure Web Apps using Visual Studio Online build, but accomplishes the deployment using a PowerShell step in the build pipeline. We want to make use of VSO Release Management vNext to be able to stage releases through different environments. This post shows how we finally got this up and running.
subscribe via RSS