Is it good choice to structure a large Asp.net MVC application using Areas?
pFrom the solution structure itself, areas are little bit confusing and
redundant. Each Area will have its own config etc. So as the areas
increases, the complexity and maintainability increases as well. Will it
be good choice to modularise or partition and MVC application
functionality in to Areas or continue with traditional Controller/View
approach?. /p pPlease suggest a common solution or better way to architect
a large scale MVC application./p
No comments:
Post a Comment