I am just back from 2.5 months unpaid leave which I used to spend time with my family. So, I almost did not spend time with software development. One exception is that I wanted to be able to configure Visual Studio 2017 to be able to debug into ASP.NET Core 2.0 source code.

After running a first console app on my Raspberry Pi 3, I had to try ASP.NET Core and API. Two weeks ago when I posted “.NET Core console app running on Raspberry Pi”, I could make API working, but I had no chance with MVC. Today it worked!

Now that there is a distribution of .NET Core on a Linux distro running on my Raspberry Pi 3, I had to try it.

In this post, I will explain all the steps I had to execute to be able to run my first Hello World application.

In the last posts, we looked at the code to build a HipChat Connect add-on with ASP.NET Core, run the solution in a Docker container and secure the access to the application with a valid HTTPS certificate that we got from Let’s Encrypt for free and finally deploy all of this on Azure!

Following my previous posts on ASP.NET Core RC2, Docker and HipChat Connect add-on and Deploying Docker containers running ASP.NET Core RC2 to Microsoft Azure Cloud I needed, as promised in the last post, to come with a solution to secure the whole with an HTTPS certificate!

Following my previous post on ASP.NET Core RC2, Docker and HipChat Connect add-on I wanted to learn the next step which is to deploy my Docker container on the Microsoft Azure Cloud!

This weekend ASP.NET Core RC2 was starting to show up! And it finally was released today. Get it fresh from here. We had here a long three days weekend with quite awful gray clouds and cold weather for the season, so a perfect excuse to get started!

I have been playing with all Docker tools for quite some time now! Started with the command line and all its commands like docker start, stop, ps, etc… Then I tried Kitematic and even compiled it from the source before it was supporting Windows! Then Docker Toolbox.

Even if online Github Pull Request is a nice and effective tool, in some situation you need to open your solution in Visual Studio to verify something.

In the past in my team, we were storing the Telerik assemblies into our SVN repository then in Git! I wasn’t happy about that for a really long time. Each releases our repository was growing much more than it was needed for nothing!