We are very pleased to announce the availability of ASP.NET Core RC2. This release succeeds the ASP.NET 5 RC1 release and features a number of updates to enhance compatibility with other .NET frameworks and an improved runtime. You can install the RC2 from dot.net.
What happened to ASP.NET 5?
This release features the rebranding of ASP.NET 5 to ASP.NET Core. This renaming was made in order to clarify that this is a new framework built from the ground up and not a revision of the existing ASP.NET frameworks. More details can be found on this blog.
Introducing the .NET CLI
A key change that occurred between RC1 and RC2 is the introduction of the .NET command-line interface. This tool replaces the dnvm, dnx, and dnu utilities with a single tool that handles the responsibilities of these tools. Get started by executing the command `dotnet` at a command-prompt:
ASP.NET Core is a console app
In RC1 an ASP.NET application was a class library that contained 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.
As of RC2 an ASP.NET Core application is a .NET Core Console application that calls into ASP.NET specific libraries. What this means for ASP.NET Core apps is that the code that used to live in the ASP.NET Hosting libraries and automatically run your startup.cs now lives 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. It also means that customers have more obvious control over the code that hosts and runs their ASP.NET Core app:
In this code snippet, from the Main method of an ASP.NET Core RC2 app, is responsible for configuring and running the app. If, for example, you want your application to listen on a particular port or IP address then you can use the WebHostBuilder to do it.
This migration from a class library that is designed to be run on the DNX to a console application with a Program.cs and a Main method that can be run by a new .NET toolchain is one of the most significant changes that RC2 brings to ASP.NET Core.
IIS Support Baked In
IIS is a tremendous web server and we continue to provide first-class support for it. Use the new ASP.NET Core Module in your web.config (it’s added in the new project templates) to configure IIS to launch and host your application.
- <configuration>
- <system.webServer>
- <handlers>
- <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified"/>
- </handlers>
- <aspNetCore processPath="%LAUNCHER_PATH%"
- arguments="%LAUNCHER_ARGS%"
- stdoutLogEnabled="false"
- stdoutLogFile=".\logs\stdout"
- forwardWindowsAuthToken="false"/>
- </system.webServer>
- </configuration>
How do I migrate from RC1 to RC2?
With these changes to the underlying framework and the branding changes, there are a number of updates that you will need to make to your applications to make them RC2-ready. We have written the following guides to help you update:
- Migrating from DNX to .NET Core
- Migrating from ASP.NET 5 RC1 to ASP.NET Core 1.0 RC2
- Migrating your Entity Framework Code from RC1 to RC2
Yes, Azure Web Applications have full support for deploying ASP.NET Core RC2 apps. More details are available on the Azure blog.
Source: microsoft.
For more information , please support and follow us.
Suggest for you:
REST WCF Service in ASP.NET
Visual Basic.Net Tutorials for Beginners
