We are wondering what is the best migration path for an ASP.NET MVC 3 project to Identity 2.0

Our current project features the ASP.NET membership with custom password reset implementation.

The migration requirements are the following:

  • We want to switch to Bootstrap without recycling anything of the current website style/layout
  • We want - obviously - to maintain the thousand membership users currently in the database

Should we:

  1. Migrate the authentication logic first, then create a new VS2013 project and copy over controllers and views for a clean Bootstrap interface

  2. Migrate to ASP.NET 4.0 first, than to ASP.NET Identity 2.0, then create a new VS2013 project and copy over controllers and views for a clean Bootstrap interface

  3. Create a new VS2013 project, copy over controllers and views then try to implement new authentication?

  4. Migrate to ASP.NET 5.0 first, than to ASP.NET Identity 2.0, then create a new VS2013 project and copy over controllers and views for a clean Bootstrap interface

Thanks.

有帮助吗?

解决方案

I would follow this tutorial which walks you through the steps to migrate from ASP.NET Membership to ASP.NET Identity. The project basically has you open the old project in VS 2013, which was what I would do instead of copying. I would also upgrade to MVC 5 using NuGet and you can add Bootstrap to your project as well using NuGet. You will have to modify your views to use the Bootstrap classes and include the Bootstrap CSS in your views or layout/master view.

许可以下: CC-BY-SA归因
不隶属于 StackOverflow
scroll top