ASP.NET MVC
Discussions center on the advantages of ASP.NET MVC over traditional WebForms, praising its modernity, performance, Razor templating, and C# integration, while contrasting it with frameworks like Rails.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Have you tried ASP.Net MVC? It's fairly decent and it isn't as heavy has webforms.
Interesting to see them using ASP.NET MVC.
ASP.NET MVC devastates all web platforms I've dealt with but rails. I realise it's a personal preference thing but you should look into it - it's open source, they got prominent community figures to design it and it lets you use C# (a great growing language) online properly without worrying about ASP.NET crap.
C++ no, C# yes: ASP.NET MVC is pretty good.
The difference between webforms and MVC was huge... (no more postbacks)But i think Microsoft is slowly finding the correct way of doing things and yes, there is a lot of influence of NodeJS (Owin) and RoR (Scaffolders). But it's easier to change between the same platform (and still using C#), then changing between web technologies.The above user wasn't required to switch to Silverlight, some web applications in my company still use Asp.Net 1.0 and it still works (not my projects,
exactly ASP.Net is a much more mature framework right now and web forms seems to be the least preferred option to build apps
What do you find so awful about ASP.net?
ASP.NET is not oldschool - it has MVC (with best templating language - Razor), real time with SignalR. Stop living in Visual Basic and Web Forms age...
Tried reading this but the site was down... ironically. I've been developing the .NET stack for 10 years now and would have to say straight ASP.NET is the easiest way to add the most horrible amount of bloat to your pages and bring about horrible performance.My gut feel is that it was made to allow application developers to build intranet sites without having to worry about the stateless nature of HTTP. The result was a woeful viewstate that got slugged between the server and client, plu
Doesn't ASP.NET MVC using Razor and Entity Framework cover all of that? Plus C# is generally really nice to work with.