AspNetCore.Docs/aspnetcore/migration/mvc.md

title	author	description	ms.author	ms.date	uid
Migrate from ASP.NET MVC to ASP.NET Core MVC	ardalis	Learn how to get started migrating an ASP.NET MVC project to ASP.NET Core MVC.	riande	04/06/2019	migration/mvc

Migrate from ASP.NET MVC to ASP.NET Core MVC

By Rick Anderson, Daniel Roth, Steve Smith, and Scott Addie

This article shows how to get started migrating an ASP.NET MVC project to ASP.NET Core MVC. In the process, it highlights many of the things that have changed from ASP.NET MVC. Migrating from ASP.NET MVC is a multiple step process and this article covers the initial setup, basic controllers and views, static content, and client-side dependencies. Additional articles cover migrating configuration and identity code found in many ASP.NET MVC projects.

[!NOTE] The version numbers in the samples might not be current. You may need to update your projects accordingly.

Create the starter ASP.NET MVC project

To demonstrate the upgrade, we'll start by creating a ASP.NET MVC app. Create it with the name WebApp1 so the namespace matches the ASP.NET Core project we create in the next step.

Optional: Change the name of the Solution from WebApp1 to Mvc5. Visual Studio displays the new solution name (Mvc5), which makes it easier to tell this project from the next project.

Create the ASP.NET Core project

Create a new empty ASP.NET Core web app with the same name as the previous project (WebApp1) so the namespaces in the two projects match. Having the same namespace makes it easier to copy code between the two projects. You'll have to create this project in a different directory than the previous project to use the same name.

• Optional: Create a new ASP.NET Core app using the Web Application project template. Name the project WebApp1, and select an authentication option of Individual User Accounts. Rename this app to FullAspNetCore. Creating this project saves you time in the conversion. You can look at the template-generated code to see the end result or to copy code to the conversion project. It's also helpful when you get stuck on a conversion step to compare with the template-generated project.

Configure the site to use MVC

::: moniker range=">= aspnetcore-2.1"

• When targeting .NET Core, the Microsoft.AspNetCore.App metapackage is referenced by default. This package contains packages commonly used by MVC apps. If targeting .NET Framework, package references must be listed individually in the project file.

::: moniker-end

::: moniker range="= aspnetcore-2.0"

• When targeting .NET Core, the Microsoft.AspNetCore.All metapackage is referenced by default. This package contains packages commonly used packages by MVC apps. If targeting .NET Framework, package references must be listed individually in the project file.

::: moniker-end

::: moniker range="< aspnetcore-2.0"

• When targeting .NET Core or .NET Framework, packages commonly used packages by MVC apps are listed individually in the project file.

::: moniker-end

Microsoft.AspNetCore.Mvc is the ASP.NET Core MVC framework. Microsoft.AspNetCore.StaticFiles is the static file handler. The ASP.NET Core runtime is modular, and you must explicitly opt in to serve static files (see Static files).

• Open the Startup.cs file and change the code to match the following:

  [!code-csharp]

The UseStaticFiles extension method adds the static file handler. As mentioned previously, the ASP.NET runtime is modular, and you must explicitly opt in to serve static files. The UseMvc extension method adds routing. For more information, see Application Startup and Routing.

Add a controller and view

In this section, you'll add a minimal controller and view to serve as placeholders for the ASP.NET MVC controller and views you'll migrate in the next section.

• Add a Controllers folder.

• Add a Controller Class named HomeController.cs to the Controllers folder.

• Add a Views folder.

• Add a Views/Home folder.

• Add a Razor View named Index.cshtml to the Views/Home folder.

The project structure is shown below:

Replace the contents of the Views/Home/Index.cshtml file with the following:

<h1>Hello world!</h1>

Run the app.

See Controllers and Views for more information.

Now that we have a minimal working ASP.NET Core project, we can start migrating functionality from the ASP.NET MVC project. We need to move the following:

• client-side content (CSS, fonts, and scripts)

• controllers

• views

• models

• bundling

• filters

• Log in/out, Identity (This is done in the next tutorial.)

Controllers and views

• Copy each of the methods from the ASP.NET MVC HomeController to the new HomeController. Note that in ASP.NET MVC, the built-in template's controller action method return type is ActionResult; in ASP.NET Core MVC, the action methods return IActionResult instead. ActionResult implements IActionResult, so there's no need to change the return type of your action methods.

• Copy the About.cshtml, Contact.cshtml, and Index.cshtml Razor view files from the ASP.NET MVC project to the ASP.NET Core project.

• Run the ASP.NET Core app and test each method. We haven't migrated the layout file or styles yet, so the rendered views only contain the content in the view files. You won't have the layout file generated links for the About and Contact views, so you'll have to invoke them from the browser (replace 4492 with the port number used in your project).

  • http://localhost:4492/home/about

  • http://localhost:4492/home/contact

Note the lack of styling and menu items. We'll fix that in the next section.

Static content

In previous versions of ASP.NET MVC, static content was hosted from the root of the web project and was intermixed with server-side files. In ASP.NET Core, static content is hosted in the wwwroot folder. You'll want to copy the static content from your old ASP.NET MVC app to the wwwroot folder in your ASP.NET Core project. In this sample conversion:

• Copy the favicon.ico file from the old MVC project to the wwwroot folder in the ASP.NET Core project.

The old ASP.NET MVC project uses Bootstrap for its styling and stores the Bootstrap files in the Content and Scripts folders. The template, which generated the old ASP.NET MVC project, references Bootstrap in the layout file (Views/Shared/_Layout.cshtml). You could copy the bootstrap.js and bootstrap.css files from the ASP.NET MVC project to the wwwroot folder in the new project. Instead, we'll add support for Bootstrap (and other client-side libraries) using CDNs in the next section.

Migrate the layout file

• Copy the _ViewStart.cshtml file from the old ASP.NET MVC project's Views folder into the ASP.NET Core project's Views folder. The _ViewStart.cshtml file has not changed in ASP.NET Core MVC.

• Create a Views/Shared folder.

• Optional: Copy _ViewImports.cshtml from the FullAspNetCore MVC project's Views folder into the ASP.NET Core project's Views folder. Remove any namespace declaration in the _ViewImports.cshtml file. The _ViewImports.cshtml file provides namespaces for all the view files and brings in Tag Helpers. Tag Helpers are used in the new layout file. The _ViewImports.cshtml file is new for ASP.NET Core.

• Copy the _Layout.cshtml file from the old ASP.NET MVC project's Views/Shared folder into the ASP.NET Core project's Views/Shared folder.

Open _Layout.cshtml file and make the following changes (the completed code is shown below):

• Replace @Styles.Render("~/Content/css") with a <link> element to load bootstrap.css (see below).

• Remove @Scripts.Render("~/bundles/modernizr").

• Comment out the @Html.Partial("_LoginPartial") line (surround the line with @*...*@). For more information see Migrate Authentication and Identity to ASP.NET Core

• Replace @Scripts.Render("~/bundles/jquery") with a <script> element (see below).

• Replace @Scripts.Render("~/bundles/bootstrap") with a <script> element (see below).

The replacement markup for Bootstrap CSS inclusion:

<link rel="stylesheet"
    href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css"
    integrity="sha384-BVYiiSIFeK1dGmJRAkycuHAHRg32OmUcww7on3RYdg4Va+PmSTsz/K68vbdEjh4u"
    crossorigin="anonymous">

The replacement markup for jQuery and Bootstrap JavaScript inclusion:

<script src="https://code.jquery.com/jquery-3.3.1.min.js"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js"
    integrity="sha384-Tc5IQib027qvyjSMfHjOMaLkfuWVxZxUPnCJA7l2mCWNIpG9mGCD8wGNIcPD7Txa" crossorigin="anonymous"></script>

The updated _Layout.cshtml file is shown below:

[!code-cshtml]

View the site in the browser. It should now load correctly, with the expected styles in place.

• Optional: You might want to try using the new layout file. For this project you can copy the layout file from the FullAspNetCore project. The new layout file uses Tag Helpers and has other improvements.

Configure bundling and minification

For information about how to configure bundling and minification, see Bundling and Minification.

Solve HTTP 500 errors

There are many problems that can cause a HTTP 500 error message that contain no information on the source of the problem. For example, if the Views/_ViewImports.cshtml file contains a namespace that doesn't exist in your project, you'll get a HTTP 500 error. By default in ASP.NET Core apps, the UseDeveloperExceptionPage extension is added to the IApplicationBuilder and executed when the configuration is Development. This is detailed in the following code:

[!code-csharp]

ASP.NET Core converts unhandled exceptions in a web app into HTTP 500 error responses. Normally, error details aren't included in these responses to prevent disclosure of potentially sensitive information about the server. See Using the Developer Exception Page in Handle errors for more information.

Additional resources

• xref:blazor/index
• xref:mvc/views/tag-helpers/intro