Phased (partial) translation of the web application with MVC3 to MVC5, or Core?

Good time of day.

There is an information system (web application) ASP.NET MVC3 (in conjunction NHibernate).
The app is working for many years, gradually refined, something is corrected, something is added, in General, everything like everyone else)
Is this thing a number of modules links in main menu are in one module or another. Use one database (MSSQL2014).
There is a need to create a new module which will generate a bunch of different reports. And then I wondered...
After all, it is time to move on to a more recent version, and that in MVC3 somehow outdated little by little. You can go to MVC5 or even on the Core.
Had this idea to write a new module on new technologies (eg MVC5 in conjunction with the Entity) in the IIS to publish it as a separate app, and the main menu will link
there. And then, little by little all the modules in the same makarom to rewrite.
Dear forum prompt:
1. Viable my idea is.
2. As better and more correct to do in my situation.
March 12th 20 at 08:10
2 answers
March 12th 20 at 08:12
Here we have code to look at, all depends on many things: how to implement the rights, roles, how authentication works. In мвс3 identiti have not been, have hands membeship provider to implement, how You are going to carry it?
And then, why on мвс5 and not directly on the crust?
Not knowing the structure, it is difficult to say for sure. But I probably would in this situation, started a new project and just quietly endured it in pieces of code that can be migrated, and wrote something new. If you move the tail, it is possible to stretch to a standstill when the kernel cannot be changed.
March 12th 20 at 08:14
Thanks for the reply. Your idea realized.
If you continue to speculate on this topic, in this phased (or partial) transfer of the project, you may encounter three main blocks of problems:
1. The problems of authentication/authorization.
2. Compatibility issues programmatic level server environment. Libraries used in the project are designed for their version .NET. Ie, a bad option is
what you may need in a separate server.
3. "Not knowing the structure, it is difficult to say for sure". Let's just say, the problem of the structure. (How strongly connected/intertwined logic, data, presentation
in different modules etc, etc.).
Approximately so, or I missed something?
@Jody_RussI saw your question, it was not in response to write, and in a comment to my answer)
You got that right. Of course, it all depends on the project, but usually everything is much easier when you transfer.
Nothing prevents You from moving your implementation of the authentication, well, only if it rigidly to something external is not tied to, nobody is forcing you to use that Identity.
The main difficulty was there to unleash different approaches, frameworks, settings, configuration. If any of the 3 does not contradict the concept core, then you can transfer as is. - grover_Windler56 commented on March 12th 20 at 08:17

Find more questions by tags C#.NETASP.NET