Comments on: What Would You Choose For New .NET Web Development?

By: walk on the seaside

walk on the seaside — Wed, 14 Jan 2009 15:51:51 +0000

This one : http://www.seaside.st/ in c# would be nice…

By: Stuart

Stuart — Wed, 31 Dec 2008 16:45:13 +0000

…or, you know… MonoRail.

By: Greg

Greg — Wed, 31 Dec 2008 16:17:06 +0000

“Question… what if the project is one that requires rapid development with a small user-base (intranet), all using internet explorer 7. Wouldn’t WebForms be the preferrable choice?”

This could be done with a Click Once Smart Client too.

By: Web development in the .NET world has gotten a lot more interesting in the last couple of years - Greg Robinson's Blog

Wed, 31 Dec 2008 16:14:45 +0000

[...] good and quick read on the 3 options by Davy Brion Posted: Dec 31 2008, 11:13 AM by gregarobinson | with no comments [...]

By: Davy Brion

Davy Brion — Wed, 31 Dec 2008 09:57:25 +0000

it depends

i would go with WebForms if _all_ of the following conditions are true:
1) you don’t have a lot of room to get up and running with ASP.NET MVC
2) the project is not very big and will require little maintenance or further development once it’s been deployed (be careful… if it was developed quickly, they’ll always think that new features can be added just as fast)
3) you already have a lot of WebForms experience

if the project is complex or if you can be reasonable sure that you’re going to get lots of changes or new features after it’s ‘completed’, then i’d go with ASP.NET MVC for the improved testability and cleaner code in general. Rapid development is only sustainable if you have a good code base, and WebForms tends to lead to messy code very quickly, even though it does get you up and running very fast.

By: Rafferty Uy

Rafferty Uy — Wed, 31 Dec 2008 01:35:53 +0000

Question… what if the project is one that requires rapid development with a small user-base (intranet), all using internet explorer 7. Wouldn’t WebForms be the preferrable choice?

I say this because though ASP.Net MVC is nice, initial development takes longer (even though maintenance is faster). Also, one of the strengths of MVC is that it’s easier to support multiple browsers, which this project does not really need.

In this case, would you still prefer ASP.Net MVC? Please tell me why. (We are in the middle of deciding what to use, so your post is really helpful!)

By: Interesting Finds: 2008.12.31 - gOODiDEA.NET

Interesting Finds: 2008.12.31 - gOODiDEA.NET — Wed, 31 Dec 2008 01:05:48 +0000

[...] What Would You Choose For New .NET Web Development? [...]

By: Juan Manuel

Juan Manuel — Tue, 30 Dec 2008 19:47:33 +0000

Nice article… I was wanting to switch to MVC, and I think this easy reading convinced me… now I’ll have to do the same with my co-workers

By: Davy Brion

Davy Brion — Tue, 30 Dec 2008 10:20:48 +0000

WPF in a browser only works on Windows

Silverlight at least works on the Mac as well (and it should work on Linux too once Moonlight works properly)

By: Reflective Perspective - Chris Alcock » The Morning Brew #253

Reflective Perspective - Chris Alcock » The Morning Brew #253 — Tue, 30 Dec 2008 07:57:43 +0000

[...] What Would You Choose For New .NET Web Development? – Davy Brion explores the options for building a web application using the .NET framework. [...]

By: Yoram

Yoram — Tue, 30 Dec 2008 07:10:50 +0000

WPF in a browser anyone (XBAP)?

By: efdee

efdee — Mon, 29 Dec 2008 16:55:33 +0000

I’m a big fan and longtime user of MonoRail, but recently I’ve been looking into ASP.NET MVC because, well, there’s no reason not to. With Hammett busy on MEF, I have no idea as to where MonoRail is headed. From a documentation point of view, you can be pretty sure that ASP.NET MVC will get the upper hand.

To me, it seems like ASP.NET MVC is moving forward pretty fast and in a better direction than MonoRail (although that’s just my 2 cents).

By: Ken Egozi

Ken Egozi — Mon, 29 Dec 2008 16:39:02 +0000

@Davy – MonoRail is here to stay. And even if myself and all other devs get hit by a bus (either the same bus, or separate buses on the same time), it’s still OSS, with a most permissive license.

MVC’s pros over MR is the MS back, and the presumably wider user base.
MR’s pros are it’s simpler and more extensible design and architecture, plus it’s proven for over two years in production environments. And it’s open-source so fixes are quick, so are feature requests.

By: Davy Brion

Davy Brion — Mon, 29 Dec 2008 16:27:15 +0000

While i like what i’ve seen from MonoRail, i do wonder about its future… how will further development proceed when most people are happy with ASP.NET MVC?

As you probably know, i’m not one to typically pick something just because it’s from Microsoft. But i have the feeling that ASP.NET MVC has more long term viability than MonoRail

Hopefully i’m wrong, and MonoRail will continue to be developed for a long time to come.

By: Stuart

Stuart — Mon, 29 Dec 2008 16:23:30 +0000

Why no mention of MonoRail? Personally I don’t understand why anyone would choose ASP.NET MVC over MonoRail, except for ‘political’ reasons (e.g. “we’re a ‘Microsoft Shop’”), and politics are about the poorest reason I can imagine to choose one technology over another.