We were used with Microsoft as being against open-source and using ‘vendor lock-in’ practices. In the past, in order to do development, you needed Windows and Visual Studio which were not cheap at all. For hosting, IIS was necessary, which, of course, required Windows.
In the last years it seems that Microsoft executives have been trying to redeem themselves by pushing for open-source, cross-platform and free development environments. Based on GitHub Latest Statistics, Microsoft is the organization with the most open source contributors, outperforming organizations like Facebook or Google.
.NET Core is not just a continuation of ASP.NET 4.6, it is a whole new framework. It is much smaller, a lot more modular, it is open source and cross platform. Compared with the previous versions, it has the advantage of including only the relevant libraries instead of the whole framework.
- Open Source – It is available here
- Cross-Platform – Runs on Windows, macOS and Linux
- Command-line Tools – Supports basic operations without needing an IDE
- Thin, fast, modular – the entire platform delivered via NuGet
Maybe you are coming from an environment that allows you to start development right away, by installing a small package ecosystem and use commands for basic operations; Node.js, for example.
You can have a similar experience with .NET Core by only installing .NET Core SDK. You will be able to manage your project using the command line.
If you are already used to Visual Studio, you can give the new Visual Studio 2017 a try. It comes with all the good stuff, including .NET Core. The Community version is for free!
If you’re concerned about the installation taking too much time, know that we redesigned the installer, allowing you to be more selective with the components you install. The minimum Visual Studio footprint was reduced and the installation is done more quickly.
The good news doesn’t end here. Visual Studio 2017 performance was significantly improved (launch time reduced with 50%). You can check the release notes here.
Let’s try the new command line tool:
dotnet new web
Simple as that. This command line flow reminds me of node package manager, which allows you to quickly setup your project. With .NET command line, you can use the same approach to create the project, manage dependencies, run and build the project. The packages are managed through NuGet (similar with npm). It feels like Microsoft tried to replicate some of the Node.js behavior. For the early versions of .NET Core, the dependencies were maintained using project.json (just like there is in Node.js), but it was replaced by the MSBuild/csproj format, which is XML based.
You can even use the command line with Yeoman, scaffolding tool for modern web apps, but you will need to install it through npm.
The project was created, let’s see how it looks:
It is pretty light, it has the .NETCore.App as a default dependency together with AspNetCore. The project also comes with a logging implementation, that is why it has another dependency for Application Insights.
We now retrieve all dependencies using NuGet and store the packages in a shared location for all projects. This caching of packages results in smaller project sizes.
Program class contains the entry point method of the application. This is where the host is setup through the WebHostBuilder. In the Startup class, you configure the request pipeline that handles all the requests made to the application.
ASP.NET Core and ASP.NET 4.6
he .NET Core 1.0 framework underwent a redesign to create a leaner and more modular framework with enhanced support for cloud-based connected applications.
It comes with many great improvements like: integration with client side frameworks, cloud ready configuration system, lighter HTTP request pipeline, built-in dependency injection, and many more.
The ASP.NET Core is no longer using System.Web assembly, it is based on a set of granular NuGet Packages. The applications have a smaller footprint, improved performance and reduced servicing.
Let’s compare the size of the newly created ASP.NET Core project, with an existent ASP.NET 4.6 project:
The differences are quite impressive. Some improvement is because of the new package management, which no longer stores packages in the project but in a centralized location. However, even after removing the packages from the old project, the size was still 14mb.
Another test was done to compare the memory usage of the IIS worker process, the Windows process which runs Web Applications.
The memory usage for the old application is about 3 times higher than the ASP.NET Core application.
ASP.NET Core MVC
If you want to spice things up a little bit, you can create an ASP.NET MVC Core project. You can do that using the command ‘dotnet new mvc’, or Visual Studio interface.
This will not only create a MVC project, but it will also use Bower for managing client-side libraries and it will come with a Bootstrap theme. Bundling and minification are also setup. You can easily add different client side libraries like: Gulp, Grunt or other.
ASP.NET Core performance increased significantly based on the benchmarks done by Techempower. On Round 13, ASP.NET was a pleasant surprise because it had the most dramatic performance improvement. For the Plain text tests, the improvement was amazing, compared with Mono, going from 2 120 requests to 18 223 600, making it 859 faster! For other tests the performance was not that drastic, but compared to previous versions, it is still pretty impressive. Microsoft has committed to a long-term plan for improving performance, so we can anticipate more pleasant surprises!
You can find an alternative test on GitHub Asp Benchmarks.
ASP.NET Core is not dependent on IIS anymore. It can be used with Kestrel, a cross-platform web server. If the application is exposed to the Internet, IIS, Nginx or Apache can be used as a reverse proxy server, which receives HTTP requests from the Internet and forwards them to Kestrel.
ASP.NET also has great support for Azure. The configuration for deploying a simple application can be done within minutes. The deploy can be done manually, by triggering a publish profile, or by using continuous integration, through Azure, for example.
You can find more details about how to publish the application to a Docker Image, or to a Linux Environment using nginx or using Apache Web Server.
ASP.NET 4.6 is a mature platform. So, if you are looking for something that is already tested and has been running large websites for some time, you should probably stick with it.
However, if you want to be on the leading edge of technology, setup faster, enjoy the performance and develop and host the application on any platform, .NET Core should be your choice. This could help you decide.
Major improvements were also made in the documentation area. The sections are much clearer, and the articles are way more descriptive and easier to understand.
Article written by Andrei Spataru