Microsoft announced on its blog that ASP.NET Core RC2 is available for download from www.microsoft.com/net and that it comes with improvements to its compatibility with other .NET frameworks, as well as an improved runtime. With this occasion, the company also announced that ASP.NET 5 will be rebranded to ASP.NET Core.

Microsoft built this framework from the ground up, the company making it clear that it’s not a revision of the existing ASP.NET frameworks. Users need to know that ASP.NET Core RC2 contains the RC2 of the .NET Core runtime, as well as libraries which end up in the “bin” folder when deploying an application.

The tooling which includes command-line, project and Visual Studio tools is now a preview 1 release and this change will be very useful for developers who use the runtime to finish their projects while all tools are completed.

The .NET command-line interface, which appeared between RC1 and RC2, has replaced the dnvm, dnx, and dnu utilities, introducing a tool that handled their responsibilities. Before becoming a console app, in RC1, ASP.NET was a class library containing a Startup.cs class. “When the DNX toolchain run your application ASP.NET hosting libraries would find and execute the Startup.cs, booting your web application. Whilst the spirit of this way of running an ASP.NET Core application still exists in RC2, it is somewhat different,” has explained Microsoft on its blog.

In RC2, an ASP.NET Core application has become a .NET Core Console application, and the code that “lived” in the ASP.NET Hosting libraries and which automatically ran the startup.cs is now found inside a Program.cs. “This alignment means that a single .NET toolchain can be used for both .NET Core Console applications and ASP.NET Core applications” clarified Microsoft, adding that now, customers can better control the code that hosts and runs ASP.NET Core app.

RELATED STORIES TO CHECK OUT:

ncG1vNJzZmivmaOxsMPSq5ypp6Kpe6S7zGiYrKhdo7K1ecKoqZ5loph%2FbrDOsKWlp5GZfA%3D%3D