Introduction

Many of you might have been developing applications in Net Core 2.0 version, as that was the main release with lots of features. But did you know that the next big release has already happened with some additional features in Net Core journey? Have you already migrated your applications to Dot Net Core 2.1.x version already? If you haven’t, no worries, here in this post, we are going to cover talk about how we can migrate/update our applications to the new version of Dot Net Core. I hope you will like this article.

Background

As I said, this post is only going to cover the steps you may have to take to update your existing Dot Net Core application to 2.1.x. And I will be not be talking about what is Dot net core? And why dot net core is important? etc, if you have those queries in your mind, I strongly recommend you to read the Microsoft document here.

We will be creating a Dot net Core 2.0 application first, and then we will update the same to 2.1.x version. Sounds good?

.Net Core 2.0 to 2.1.x

Let’s create a .net core 2.0 application

As usual open your favorite IDE, Visual Studio 2017, Click on File -> New Project

As you can see, Asp Net Core version is 2.0.

You can even check the version in your application properties.

Now let’s run our application and see the output.

Update Visual Studio 2017 to the latest

As a first step, to work with Dot net core 2.1 you need to update your IDE. There are a couple of ways you can update your IDE, but the easiest way is to go check the Notifications panel. Let’s see how to do that.

Go to the View tab and click on Notifications

Now you can see all the notifications here as shown in the below image. I always update my Visual Studio whenever there is an update, so you won’t be able to see that notification here on my panel. If you haven’t updated, and if you check the Notifications panel, I am sure you will get a link to the update here. You will be able to do further.

Once you have updated, you can verify your version.

Install latest Dot Net Core

Here I am going to download the latest version from here, however, you can select which version you want from here.

As you can see that we have installed Dot Net Core SDK, Dot Net Core Runtime, Asp Net Core Runtime, and now you can see that the new version is available for you in Visual Studio 2017.

Changing the Target frameworks

As the first step, we need to change the Target framework for our application. Here you can select it in the Properties or you can edit the dot(.)csproj file.

Now it is time to change the Microsoft.AspNetCore.All to Microsoft.AspNetCore.App, as with this version Microsoft have reduced the number of dependencies. We always need to install only the needed things right, instead of everything.

You will always need to change all of your references to the new version. Here I just wanted to show how you can do that. So, look into the packages you have in your application and change it accordingly.

What is new in Dot(.) Net Core 2.1.x

The Dot Net Core 2.1.x is a release with some cool new features, I strongly recommend you to read those here.

I may write a new post with this features soon.

Conclusion

Thanks a lot for reading. Did I miss anything that you may think which is needed? Could you find this post as useful? I hope you liked this article. Please share me your valuable suggestions and feedback.

Your turn. What do you think?

A blog isn’t a blog without comments, but do try to stay on topic. If you have a question unrelated to this post, you’re better off posting it on C# Corner, Code Project, Stack Overflow, Asp.Net Forum instead of commenting here. Tweet or email me a link to your question there and I’ll definitely try to help if I can.

Kindest Regards
Sibeesh Venu

Introduction

Here, in this post we are going to a see how we can install Asp.Net Core Docker in our Windows. Before we start, it would be useful if we say something about the Docker right? Docker is a container software platform where container is everything we need to make our software run. The container is light in weight. You can read more about the Docker here. I hope you will like this. Now let’s begin.

Background

Today, I was just trying to create a Asp.Net Docker application in Visual Studio 2017. Unfortunately I was getting an error as preceding.

Error MSB4018 The “PrepareForBuild” task failed unexpectedly.
Microsoft.DotNet.Docker.CommandLineClientException: Unable to run ‘docker-compose’. Verify that Docker for Windows is installed and running locally. For troubleshooting, please review http://aka.ms/DockerToolsTroubleshooting. —> System.ComponentModel.Win32Exception: The system cannot find the file specified

Then I came to know that I have not installed Docker in my machine yet, so I decided to do that.

Asp Net Core Docker Error

Installing Docker For Windows

You can install the Docker from here. Once you downloaded the set up file, please run the file.

Docker For Windows

Start and test the Docker

Once you installed the Docker, now it is time to test whether everything is installed correctly or not. Before that make sure that the Docker is starting.

Docker is Starting

There is a hight possibility that to get an error “Hardware assisted virtulization and data execution protection must be enabled in the BIOS” as preceding image.

Docker Error

Before you go and change the settings in BIOS, check in Task Manager window as well.

Hyper V support and Virtulization

Enabling Virtulization in BIOS

To Enable the Virtulization in BIOS, go to System Configuration -> Click on Virtulization Technology and Enable it.

BIOS Settings

After the restart, the Docker will ask you to start the service. Go ahead and do that.

Setting up Docker

Docker Service Is Not Runnig Window

Now again, if you are getting an error as “Error MSB4018 The “PrepareForLaunch” task failed unexpectedly.
Microsoft.DotNet.Docker.CommandLineClientException: Creating network “dockercompose3875147227_default” with the default driver
Building linq_basic_to_advanced Service ‘linq_basic_to_advanced’ failed to build: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).”, you need to change your shared drive settings in Docker.

Right click and click on the settings.

Docker Settings

Click on the Shared Drives and  select the drive that hosts your project and the drive where %USERPROFILE% resides.

Shared Drive in Docker

Click on Apply and type your filesystem passwor in the following pop up. Now if you are running the Edge version of Docker Community Edition for Windows, after the install you may be able to login with your Docker ID and password.

Docker SignIn page

We have enough settings for now, shall we just check whether the installation is done perfectly or not? To check, go to the command window and type the command as  docker run hello-world.

Docker Check From Command Window

You can also check the Docker version with the command docker –version

Conclusion

Did I miss anything that you may think which is needed? Could you find this post as useful? I hope you liked this article. Please share me your valuable suggestions and feedback.

Your turn. What do you think?

A blog isn’t a blog without comments, but do try to stay on topic. If you have a question unrelated to this post, you’re better off posting it on C# Corner, Code Project, Stack Overflow, Asp.Net Forum instead of commenting here. Tweet or email me a link to your question there and I’ll definitely try to help if I can.

Kindest Regards
Sibeesh Venu