Reputation: 391276
We have a web application written in ASP.NET for .NET 3.5, using standard web forms.
Going forward we want to start building new features, and over time migrate existing features, in ASP.NET MVC.
Is such a thing doable? Can we add the necessary files to an ASP.NET web application and thus "upgrade" it to be compatible enough with MVC so that we can start adding routes, controllers, views, etc.?
The old site is using a frameset containing a top header, a left menu, and a main content. What I envisioned was to create a new masterpage for all the existing pages, integrating all of those things into each page instead, and then start adding new pages using views instead.
I understand that unless we upgrade to .NET 4 we cannot use MVC 3, so the way I see it we have the following options:
Note that a full rewrite is out of scope at the moment, so some transitional period is the only option we can do right now.
Option 2 and 3 are the ones we want, the rest are just for completeness.
Are those options feasible? Do we have other options I haven't thought of?
Upvotes: 3
Views: 513