Is Asp.NET MVC Not Suitable For N-Tier Architecture? [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 8 years ago.

Improve this question

Firstly, I have a question which already I know the answer but I want to ask; Which one is manageable on HTML source?? Asp.NET Web Forms or Asp.NET MVC??

My second and important question; Think a project which is big and expandable web project.. You sell something and control your agents with this project. You can give XML for your product range, and you would be able to add new products.. What does "Asp.NET Web Forms is more suitable for N-Tier Architecture and Asp.NET MVC is not" mean??

Answer 1

I would say that MVC is just as suited if not more so than Web Forms. Given the much clearer separation of the different parts in the MVC framework it lends itself very well to creating a solid N-tier solution. But with anything, if care is not taken in the implementation it really doesn't matter what framework you are using.