ASP.NET MVC 1.0 Released

http://haacked.com/archive/2009/03/18/aspnet-mvc-rtw.aspx

by yaakov • 17 years ago

34 23 17 years ago

haacked.com

rlm• 17 years ago

Amazing how timing changes the amount of points given to the exact same story :D

http://news.ycombinator.com/item?id=523053

AlexTheFounder• 17 years ago

Timing is king. For MS it means that they have to adapt to new trends faster if they don't want their products abandoned.

MVC is a really big step forward, something that most people didn't expect from MS (meaning the inclusion of third party stuff).

metachor3• 17 years ago

Also the fact that the ASP.NET MVC framework is itself open sourced (the code is available on Codeplex).

I've been using this framework for a recent project at my day job and it's definitely a step in the right direction (i.e. toward design patterns common in other popular web development frameworks such as MVC, pluggable ORM system, use of third-party libraries such as jQuery, clear separation of concerns, and a strong focus on test driven devlopment).

CarlHoerberg• 17 years ago

This a great framework, i've been using it for over a year now. It's been iteratively released (to public) 10 times, which is a new way for MS to develop, and they have really listened to the feedback from its users.

Visual Studio + asp.net mvc is a highly efficient dev. enviroment.

9oliYQjP4• 17 years ago

I agree. It's great because it's essentially Rails ported over to .NET. That's not a backhanded compliment. I think it was the right thing to do. I know there are a bunch of Rails skeptics out there, but as far as development practices go, they made solid decisions at every step. Coming from conventional ASP.NET over to ASP.NET MVC should be a breath of fresh air. No more having to program on a platform that tried (and IMHO failed) at making web development be more desktop-development-like.

I've already decided against doing ASP.NET development on my own projects, but if I were forced to use ASP.NET, I wouldn't think twice about choosing the MVC version over the conventional one. I had already begun introducing the Castle frameworks (inspired by Rails) into ASP.NET projects well before ASP.NET MVC was even announced, so I can't help but praise MS here.

wayne• 17 years ago

Awesome framework. All the quirkiness of ASP.NET is abstracted away from you (though you can still get to it if you need to). As a Rails developer you'll feel right at home with controllers, views, routing, and tests.

The annoyances:

- ActiveRecord has its downsides but it's easy to use and ASP.NET MVC doesn't come with a similar ORM. LINQ is awkward to learn.

- It doesn't have view partials.

johns2• 17 years ago

No partials? Or no subcontrollers? What's wrong with RenderPartial() and RenderAction()?

johns2• 17 years ago

Use SubSonic if you want ActiveRecord.

StrawberryFrog• 17 years ago

LINQ I found is not that awkward to learn. It's a feature of C# and .net not just of asp.net MVC, so it's a transferable skill, and an important skill for .Net programming in general.

snprbob862• 17 years ago

Linq is freaking sweet. I miss it every weekday I have to write C# 2.0 and every weekend I write Python. Anyone interested in pragmatic programming languages owe it to themselves to learn a bit about Linq and why it is so pleasant to use.

The best way to learn Linq is with the 101 samples [1], but I might be bias because my friend wrote them [2].

[1] http://msdn.microsoft.com/en-us/vcsharp/aa336746.aspx

[2] http://www.microspotting.com/2007/12/anders-hejlsberg-intern

9oliYQjP4• 17 years ago

I haven't used Python since 2004, and never became an expert. But isn't is possible to achieve most of what LINQ does in Python? I know in Ruby it's possible to call sort with a block (http://snippets.dzone.com/posts/show/2120). IMHO, that code resembles the spirit of LINQ. That's without even touching on the ActiveRecord portion of Rails which achieves a lot of what LINQ does too. There's got to be a way to do this sort of thing in Python too, even if it requires a third-party library.

UPDATE: Here's a better example for Ruby syntax compared to LINQ.

http://intertwingly.net/blog/2005/09/29/Ruby-1-8-vs-LINQ

metachor3• 17 years ago

Try the ADO.NET Entity Framework, Microsoft's new LINQ-based ORM tool, released with Visual Studio 2008 SP1. It's very easy to use, and plays well with ASP.NET MVC.

misterbwong• 17 years ago

I've worked almost exclusively as a webforms programmer for the last few years and transitioning to this over the last month has been surprisingly challenging for me. I'm definitely a newbie to the "real" web and I never knew how much of the web webforms actually hid from me.

Despite the difficulties, I've been encouraged by the flexibility of MVC and am thinking about making it my framework of choice for my coming projects.

IMO, the best bits of MVC are:

-Separation of concerns. No more mixing business logic with the presentation ("view") layer. I can swap out layers of my architecture more easily

-More control over page elements. I always found the ASP.NET controls a bit lacking...

-Leaner apps. I understand that this is mostly the developer's fault as there's always a way to do things better, but most of the apps I've seen written in webforms just feel bloated. There's too much cruft built into and around webforms to make it seem desktop-y

-Better support for TDD. I've not used this part of it yet, but the MVC model does lend itself to TDD much better than webforms.

I'm not saying that WebForms will be completely gone from my development cycle, though. It is still good for many things. I think the most glaring benefits are:

-Rapid development for internal/quickie apps. This may just be my experience and familiarity talking but it's very easy to throw up a quick and dirty app with webforms. Great for internal projects.

-Legacy applications. This benefit will fade over time, but I was hearing that there were problems with MVC on II6. Also, I don't believe it's supported on any version below II6.

cdeutmey• 17 years ago

I'm having a hard time getting excited about this. In 3 months MS will release version 1.1 and then version 2 coming 6 months after, each with version compatibility issues with the release before. Then a new flavor of the month will catch MS's attention and this will finally stabilize to the point where it can be implemented or identified as junk technology.

noblethrasher• 17 years ago

Maybe, but it is open source and was developed with constant feedback from the developer community so that indicates something of a new direction on the part of MS.

c0un7d0wn• 17 years ago

What are the advantages of this over Castle Monorail?

jpcx01• 17 years ago

Big win for Microsoft. Though I'm skeptical about whether the VB focused ASP.net dev community will adopt this over the fundamentally broken "WebForm" piece (Microsoft hasn't taken any official position over which one is prefered).

Still, I've gone through this and its very well architected. Not going to get me to switch back to ASP.NET from Rails/Merb, but its nice to know that some people at Microsoft finally understand how to build a well built web development framework.

ASP.NET MVC 1.0 Released

Related Stories