Wow what a title, but it does explain that this post covers debugging the full .net framework application (not .net core) running on a Server Core container (not Linux) from the comfort of a Windows 10 Pro machine running Visual Studio 2015 and Docker for Windows.
Running remote tools on a machine and attaching is a pretty straight forward task, but there a re a few hurdles in the way when doing it on Windows Server Core 2016 container, but once it is scripted it is pretty painless.
Firstly we need a decent Docker image to start with, luckily the guys at Microsoft have created the Microsoft/aspnet image we can start with so lets build up our dockerfile
RUN mkdir C:\site
This gets the base image and creates directory that we are going to use for our web files....more
Up until late last year I was experimenting with Docker container on Windows 10 and Server 2016 using the Experimental version of Docker. Well things took a turn for the worst and basically Docker refused to run and kept crashing. Life being as it is I went onto other things and have only just come back to Docker and installing the release stable version (17.03.0-ce-win1 (10296)) I get this when switching from Linux containers to Windows:-...more
Entity Framework code first migrations are really handy, but can be dangerous in the wrong hands as they make changes to the underlying database of your application.
Before the days when a single check in would run through the build process CI/CD pipeline, it was normal for the development stage to make constant changes to a database structure as an when the features requested needed it. With the new model of all changes running through the CI/CD pipeline, the database changes could be quickly pushed to a test or staging server in no time at all. With this new model of writing code, a few precautions have to be taken to make sure EF migrations don’t wreck havoc on the database running the staging or test servers....more