Containers for Existing .NET Apps Part 1

Build with an Azure free account. Get USD200 credit for 30 days and 12 months of free services.
Start free todayThis is the second of a two part series where Robert is joined by Aditi Dugar, who shows how and why you can modernize existing .NET applications by containerizing them and moving them to the cloud. This brings significant deployment and DevOps improvements without the need to re-architect or rewrite the app.
In part one, Aditi showed how to create containers to run existing .NET applications. In part two, she shows how to get those containers running in Azure and introduces us to using Kubernetes to orchestrate the containers.
Resources:
This is seriously misleading video. Windows containers are NOT production ready anywhere but hosted either in docker swarm or service fabric. Kubernetes support for windows containers are in beta stage and you will not get support from any of the vendors running windows containers in kubernetes. If you want to have supported production ready as mentioned in the video container orchestrator then you have only 2 choices and swarm actually is most mature out of those two.
@artisticcheese:You're correct - Kubernetes support for Windows Containers is still in preview at the moment. This was pointed out in the overview slide that called out Windows containers as less mature in Kubernetes, as well as Robert's follow up comment that this is still an active work in progress. Thanks for clarifying this.
At this point, for mature Windows Containers support, we would recommend Service Fabric, which will also allow you to stay in the Microsoft ecosystem.
This is great Aditi if I have access to the source code but how do I bring a legacy app into the Container ecosystem if I don't have access to the source code?