Is MVC Applicable for .NET?

Hi there,

I like to solicit some feedbacks on MVC within context of ASP.NET.   My observations says that many still prefer to code their aspx pages as stand-alone pages, with html links to other pages hard-coded within these pages. 

An alternative is of course to use a Front Controller pattern, or an MVC framework to overcome this.  One example is NMaverick (a port from java) and UIP App Block. However, this usually require much up front architectural codes or framework to work.

In the J2EE world, Struts is almost a requirement in any enterprise level application.  I was a fan of Struts, and is wondering why there isn't a port of this to .NET.  Is it becoz it is not applicable? Maybe the benefit does not justify the effort?  If there is a MVC framework available, would you consider using it in your projects? What are you factors of considerations then: ease of use, maintenability of your codes etc.

Thanks.

Yes, it is still applicable to .NET.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpatterns/html/DesMVC.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpatterns/html/ImpMVCinASP.asp

Maung Maung

MaungMaung wrote:

http://msdn.microsoft.com/library/default.asp?url=/library/enus/dnpatterns/html/ImpMVCinASP.asp

When I first tried to find how to implement MVC in ASP.NET, I read that article and many doubts started floating in my mind. Initially, I had doubts about how MVC is loosy implemented using code behind. I even went to an extent of implementing what I considered a MVC design pattern on ASP.NET, by designing controllers to handle every specific event request.

For e.g. for a page load event, I devised a controller class (e.g. LoadXXXController.cs) which is inherited from my abstract Controller class with a simple method called Action. Thus, in the page_load event, it simply called objLoadXXXController.Action ().

It's really neat and easy to code, that is if you have a minimum team size of 3-4 person. Of cos, it gets rather confusing during debugging, as there are so many possible controllers behind each .aspx page.

Actually, if u think abt it.. if you use WF, it is very similar to a MVC model.

Wee Hyong,

It's WF.

Firedancer wrote:

Wee Hyong, It's WF.

FD,

hahaha.. old term of reference is hard to change... heheheh..