This post is in Draft Mode - it will not appear on the site or in search results

Deploying a .Net Core Application



.Net core is the successor to the .Net framework. We are transitioning to developing in .Net core and when possible we will port existing .Net applications. There are significant advantages to using .Net core but also differences that necessitate a change to some of our deployment processes.


.Net Core gives us the option to deploy as Framework dependent or Self-contained. For a Self-contained deployment, .Net does not need to be installed on a machine in order for the application to run. This is because it is deployed with the applications dependencies included. This also means that applications from different versions of .Net Core can be installed on the same machine. This lighterweight deployment model is particulary useful when deploying in containers.

Smaller Deployments

As is noted in the article linked above, self contained deployments are larger as they need to bring along all of the applications dependencies. Even if the size of the files is not an issue, the number of files alone can make the deployment process cumbersome and make mistakes more likely.


This problem of a large number of files in .Net Core self contained deployments is described in this article Also described in this article is the Warp tool that we are currently using. This tool packages up multiple dependencies into a single file for a smaller easier to manage deployment.

Batch Files

This tool needs to be installed and run using the command prompt. After publishing and using warp to create a more compact deployment, the next step is simply moving the files to thier intended location. Since every one of these steps can be completed in command line we have decided to create a batch that includes all of the statements needed to deploy a .Net Core application using Warp. A batch file is a series of command prompt commands written in a text editor and saved with the .bat extension. Opening a batch file executes the commands as if the user executed them in the command line. Note that the commands will execute starting in the folder the batch file was when it was opened.