We have a web application written in ASP.NET for .NET 3.5 using standard web forms.
In the future, we want to start creating new functions and eventually transfer existing functions to ASP.NET MVC.
Is such a thing doable? Can we add the necessary files to the ASP.NET web application and thus “update” it so that it is MVC compatible enough so that we can start adding routes, controllers, views, etc.?
The old site uses a set of frames containing the top header, left menu, and main content. What I assumed was to create a new homepage for all existing pages, instead integrate all of these things into each page, and then start adding new pages using the views.
I understand that if we do not switch to .NET 4, we will not be able to use MVC 3, therefore, as I see it, we have the following options:
- Create a new website, somehow automatically log in to the new site with the same credentials when entering the main site and in the link between the sites. I see a lot of problems with this solution.
- Integration of ASP.NET MVC 2 into existing software, adding the necessary files and starting adding new content in the MVC style, only fixing critical errors in old files and over time transferring them to MVC.
- Switch to .NET 4 and integrate ASP.NET MVC 3, the rest is the same as option 2.
- Wait until we can plan a complete rewrite, most likely it will not happen in the foreseeable future.
- Do not do this, save web forms.
Please note that a complete rewrite is not currently available, so a transition period is the only option we can do right now.
Options 2 and 3 are the ones we want, the rest are for completeness only.
Are these options possible? Do we have other options that I haven't thought about?