All geek questions in one place

How to organize an ASP.NET MVC project to enable a lightweight version

I am migrating a web form application in ASP.NET MVC. In the future, we can offer a "lite" version of this application. This is a rather vague concept, but I expect the base database to be the same, we only simplify the user interface, and users can even switch between full and light versions.

We obviously would like to use as much as possible, possibly using the same model, but different types. Some pages will remain exactly the same, others can be eliminated or combined with other pages.

What I want to avoid is to organize the project in such a way that it complicates the implementation of this "lite" version if it leads to the fact that we decided to do it. At the moment, everything I can think of has areas for controllers and views organized by "full", "lightweight" and "general."

Does anyone have experience with multiple application variations using MVC?

+3
source share
2 answers

The best solution would be to create a custom homepage and much more in that you can create a custom post for mobile applications. See here:

http://www.hanselman.com/blog/MixMobileWebSitesWithASPNETMVCAndTheMobileBrowserDefinitionFile.aspx

.

+2

ASP.NET MVC Areas . MVC 1, , MVC 2.

0

Source: https://habr.com/ru/post/1736569/

More articles:


All Articles