{"id":2770,"date":"2016-06-30T16:04:34","date_gmt":"2016-06-30T14:04:34","guid":{"rendered":"https:\/\/sii.pl\/blog\/?p=2770"},"modified":"2023-08-18T17:05:19","modified_gmt":"2023-08-18T15:05:19","slug":"microsofts-revolution-asp-net-core-1-0","status":"publish","type":"post","link":"https:\/\/sii.pl\/blog\/en\/microsofts-revolution-asp-net-core-1-0\/","title":{"rendered":"Microsoft\u2019s revolution \u2013 ASP.NET Core 1.0"},"content":{"rendered":"\n

Dear .NET developers \u2013 big changes finally came! Open source and cross-platform .NET? Yes! Let me introduce ASP.NET Core.<\/strong><\/p>\n\n\n\n

Don\u2019t get confused! The naming of ASP.NET versions is changing \u2013 the new version is still called ASP.NET 5 but as soon as all of the parts will be ready to distribute the name will be officially changed to APS.NET Core 1.0. What about the versions of MVC and Web API? Those will no longer be problem \u2013 MVC and Web API are now included in ASP.NET Core and they all share one version as parts of one single framework. For purpose of this article I will use the final naming \u2013 ASP.NET Core 1.0.
ASP.NET Core can run on both .NET Framework and .NET Core.<\/p>\n\n\n\n

.NET CORE 1.0<\/h2>\n\n\n\n

.NET Core is not another version of .NET Framework, it is not improving the previous version and doesn\u2019t replace it. This is totally new approach \u2013 .NET Core 1.0 is a small, modular runtime that includes some parts of the .NET Framework. It is optimized for server and cloud workloads. It is a new line of .NET and it will be developed and supported as well as the .NET Framework line.
And the most surprising thing is that \u2013 unlike any other version of .NET Framework \u2013 .NET Core is open source<\/b> (both runtime and framework libraries) and cross-platform<\/b> (supported on Windows, Linux and Mac). And that makes it the Microsoft\u2019s revolution!
.NET Core contains CoreFX \u2013 set of libraries and CoreCLR \u2013 which is Common Language Runtime. Both parts are distributed via Nuget.
CoreFX<\/strong> \u2013 each of the library in the set is designed in order to requiring as little dependencies as possible which allows to include into your application only those of CoreFX that you actually need.
CoreCLR<\/strong> \u2013 the main advantage of .NET Core is its portability assured by CoreCLR \u2013 it can be packaged and deployed with your application. It doesn\u2019t require any version of .NET installed. Furthermore multiple application can be hosted side-by-side using different versions of CoreCLR and they can be upgraded individually.
.NET Core supports set of languages, especially C#, VB and F#, as well as language features \u2013 like generics, LINQ, async support and many more.<\/p>\n\n\n\n

ASP.NET CORE 1.0<\/h2>\n\n\n\n

ASP.NET Core is a framework for building modern Web applications. It was created in particular for cloud-based apps. It consists of modular components which results of making web apps that are not excessive \u2013 as we must include only those parts that we actually use. That keeps the flexibility of the app.<\/p>\n\n\n\n

\"asp\"<\/a><\/figure>\n\n\n\n

<\/p>\n\n\n\n

Your first ASP.NET Core application \u2013 it\u2019s very easy to start! And you can use Community edition of Visual Studio and ASP.NET Core \u2013 both available for free. Running the application on the localhost using IIS Express didn\u2019t change from previous versions of framework.
Significant changes start from file structure of the project. ASP.NET Core works on file system \u2013 it detects any code changes (from and outside VS), compiles into memory and loads the app \u2013 which helps with faster developing. Let\u2019s start with checking the main folder of the app \u2013 there are:
\u2022 Solution file (.sln extension typical for VS)
\u2022 File global.json which contains configuration
\u2022 The src folder containing the source code
The configuration files are written in the json notation (JavaScript Object Notation) \u2013 so they are more light than XML files.
The global.json<\/strong> file generated for new project look like that:<\/p>\n\n\n

\n{\n\"projects\": [ \"src\", \"test\" ],\n\"sdk\": {\n\"version\": \"1.0.0-rc1-update1\"\n}\n}\n<\/pre><\/div>\n\n\n
The projects<\/strong> setting indicates where are located folders containing the source code. From default there are src folder for sources and test for unit tests project. Newly created project has its source files in src folder. Within the listed folders there will be searched projects of the solution.
The sdk<\/strong> setting specifies the version of the DNX (.Net Execution Environment) which is used for opening the solution.
Inside the src folder there is exactly the same content as in the solution folder \u2013 and since ASP.NET Core works on file system adding (or deleting) a new file into the folder adds (or delete) this file to the solution as well. There is no need to build the app \u2013 all you have to do is refresh the browser to see the modifications.
One of the breaking changes about the configuration files was replacing .csproj file by .xproj and project.json files. Both files concerns only a project and not the solution. However this idea was improved in version RC2 eventually it has been decided to return to original .NET configuration \u2013.csproj file for newer versions. But as the RC2 version is the latest (during writing this article) the project.json still oblige let\u2019s take a look at some of its parts:<\/p>\n\n\n
\n{\n(\u2026)\n \n\"dependencies\": {\n\"Microsoft.NETCore.App\": {\n\"type\": \"platform\",\n\"version\": \"1.0.0-rc2-*\"\n},\n \n\"tools\": {\n\"Microsoft.AspNetCore.Server.IISIntegration.Tools\": \"1.0.0-preview2-final\",\n\"Microsoft.EntityFrameworkCore.Tools\": \"1.0.0-preview2-final\",\n\"Microsoft.AspNetCore.Razor.Tools\": \"1.0.0-preview2-final\",\n\"Microsoft.Extensions.Caching.SqlConfig.Tools\": \"1.0.0-preview2-final\",\n(\u2026)\n},\n \n\"frameworks\": {\n\"dnx451\": { },\n\"dnxcore50\": { }\n},\n(\u2026)\n}\n<\/pre><\/div>\n\n\n