MVC in c#

[dami.gupta]

Perhaps this has already been discussed to death - but thought I would
bring it up anyway.

Some Visual Studio features, e.g. the DataBindings features are the
very antithesis of the MVC pattern. With visual controls and data
sources so intimately connected, it is very easy to implement a
project with GUI and db strongly tied. Of course this becomes a
nightmare to refactor.

Does Visual Studio actually advocate the non-MVC model? A developer
has to work from scratch to implement MVC in a Visual Studio project.
Is DataBinding actually used in any non-trivial application?

Look forward to hearing some input.

 

[Jon Skeet [C# MVP]]

Perhaps this has already been discussed to death - but thought I would
bring it up anyway.

Some Visual Studio features, e.g. the DataBindings features are the
very antithesis of the MVC pattern. With visual controls and data
sources so intimately connected, it is very easy to implement a
project with GUI and db strongly tied. Of course this becomes a
nightmare to refactor.

Does Visual Studio actually advocate the non-MVC model? A developer
has to work from scratch to implement MVC in a Visual Studio project.
Is DataBinding actually used in any non-trivial application?

Look forward to hearing some input.

I think you might be interested in this:

http://weblogs.asp.net/scottgu/archive/2007/10/14/asp-net-mvc-
framework.aspx

I haven't looked at it myself, admittedly...

 

[Peter Bromberg [C# MVP]]

Visual Studio, by itself as released, is not designed to support the MVC
pattern. This is only implemented as an add-on which isn't finalized.
Personally, I like the concept but have no particular compulsion at present
to go through the pain of adopting it. However, if you must, you can find
samples on the codeplex.com site.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
MetaFinder: http://www.blogmetafinder.com