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 9 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??
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.
Related
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 3 years ago.
Improve this question
I am new in ASP.NET MVC Core and have a small query regarding ASP.NET MVC Core framework.
Is it the best way to use a separate class library for Controllers in ASP.NET MVC Core framework?
Can anyone help me to provide some detailed Pros and Cons for a separate class library for Controllers?
There no reason to do this because what exactly are you separating? The controllers that you write are going to be specific to ASP.NET MVC so you can't reuse them with another framework. There are no pros, you are just making your project more complicated for no reason.
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 9 years ago.
Improve this question
I have already learned asp .net webform and have created projects for college on it but I recently discovered asp.net MVC.
I tried to learn it but it seems way to different in terms of how you build the application and there's a steeper learning curve.
If I have already done asp.net, do I need to learn MVC as well taking in account the future real life projects I might have to do?
Thanks.
You can build any web application using the asp forms.
MVC is great, you don't need to learn it, but if you do you will enjoy it much better than web forms because it is much closer to how web works. I believe that in few years it will be more popular than regular ASP forms.
MVC with Razor gives you more control on the rendered HTML, but on the downside if you don't know HTML and CSS then it is easier to just drop the ASP controls.
One other advantage of the MVC 4, is adding the web API services. Learning MVC is a must to know how to write these useful services.
Well explained pros of mvc on below link
http://www.asp.net/mvc/tutorials/older-versions/overview/asp-net-mvc-overview
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
These days my friends recommend me to use ASP.NET MVC, instead of ASP.Net Web-forms.
But I'm not Optimist to it.
I consulate about this problem and my friends said me that these two technologies have their own place in web programming zone, according to the project type.
Now I want to know what type of projects are better to be developed by ASP.Net MVC?
and the 2nd question, In your opinion is it conceivable that Microsoft abandon this technology?
Nowadays i always use mvc for all my new projects it is much more cleaner code. And you dont have to rely on asp.net web controls i dont think web controls render nice html.
Plus that you dont have to think about viewstates.
ASP.NET mvc can apply on all type of projects it is more the way how you like too code then which type of project. Thats my opionen.
I doubt very much it will be abandoned any time soon.
MVC is a different way of working and probably more suited to a kind of developer as well as a kind of project. It gives better control over your markup and front end code, forces better practice for separation of concerns and hands over a lot more power over how the site works.
This is a broad subject and better suited to https://softwareengineering.stackexchange.com/
If you rely a lot on the ASP.NET Web Controls then you may find MVC difficult to get to grips with at first.
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
which is future of web technology of microsoft
silverlight or mvc asp.net i am really confused
iam good in asp.net but completely unaware with silvelight and mvc
Silverlight is a RIA technology from Microsoft, best thought of as a Flash competitor. It uses XAML as a markup language.
MVC is a software pattern, but also used as part the name of a web application framework by Microsoft that utilizes this pattern - ASP.NET-MVC. It is an alternative to webforms (ASP.NET) - noted for being easier to write tests for and for plug-ability of IoC containers, view engines and more.
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 5 years ago.
Improve this question
I know what is ASP.net and I know what is MVC and some other Design patterns , my question is why did microsoft choose this design pattern ? why not ASP.net 3tiers or ASP.net AOP ...etc is it easier to program with , more powerful for building websites? in other words what are the advantages to use MVC instead of other Design Patterns with ASP.net?
MVC is a strong pattern and has proved very popular in other development communities including but not limited to Ruby on Rails. Wikipedia has a long list of MVC web frameworks. I guess Microsoft, didn't want to be left behind as more and more people migrated away from WebForms.
My guess would be that it is a proven and very suitable pattern for the web. MVC fits very well with the stateless nature of the http protocol. And many other big web frameworks for other languages use the MVC pattern.