I'm just starting to learn it. Still wondering if I might switch to
MVP. ( Catharsis
http://www.codeplex.com/Catharsis , or MVC#
http://www.mvcsharp.org/Overview/Default.aspx )
Well, I'm mixed. I think it's great for applications with many pages
(many ControllerActions and many Views), and the the model is nice to
learn, but it feels like the design-time environment doesn't help much
for development. Although, I rather like having no viewstate, and the
model "feels" rather clean.
Also realize IIS 6.0 doesn't work (without some extra work). I got it to
work with a combination of mapping the .mvc extension, and installing a
redirecting filter.
Also I find it annoying that the URLS sometimes seem hard to specify
correctly. ~/Controller/ViewName doesn't seem to work in many places
(eg. forms). But I might be doing something wrong.
Lack of documentation built-into Visual Studio can be an issue... for
example, knowing how to create typed views. It's not hard; watch the
asp.net/mvc videos and you'd know.
But I got over most humps.
I don't really have much to say on this; I'm too new. This is interesting:
http://greggalipeau.wordpress.com/20...nd-aspnet-mvc/
ChevronBoyde wrote:
Hi All
I am a systems architect that has been on a 3 year extended sabbatical
from development and I am busy with a new project.
I am designing a new event website and need some advice on some of the
new architectures. There seems to be a lot of hype around MVC at the
moment, but see we are still in beta. I fear for the Tag Soup I see
unfolding and remember how MS pushed us away from that in the 90's. Are
there any issues with AJAX in MVC?
I am trying to get some advice from people who have developed any
projects using MVC and what shortcommings they had.
Thanks,
Chev