mrfleck

dpant

ps: prove me it is optional.

If you had taken the time to even take a high level look at MVC, this would already be "Proven" for you.Part of the power of this framework is that everything is pluggable even the view engine. MVC comes with the asp view engine, but you can plug in any view engine you like. There are several out there and you could even write your own. We are in early CTP here, I have no idea how you can come in and rant just because you don't get it. I would refer you to http://forums.asp.net/t/1220045.aspx for some additional discussion from some folks similar to yourself. Just because you don't like something does not mean you should run in and rant all over the place, especially when it is obvious that you have done no research on the framework other than seeing a set of code blocks and freaking out because you think this might replace your framework of choice. But don't worry, this is just an option and for those of us that see the advantage of this type of framework, we are glad to have the option.

Listen pal, I have been working with asp(.net) since ever and yes I can come in and say my opinion much like you can say yours. Most of you guys forget that ASP.NET revolutionized the web when it first came out. Noone, i repeat -noone- wants to refill html forms manually, this is a huge leap backwards. So far this is what this 2nd mvc preview is all about. There may be certain testing advantages but what we want is all our asp.net components, architecture and lifecycle that bring HUGE benefits to RAD web development. There are certain types of websites -if not most of them- that can be created in asp.net in a fraction of time compared to mvc and with a vastly better and richer interface. Of course the mvc is not yet finalized -even the Html and Url helpers are incomplete, and I think everyone expects much more to come. But I cannot just sit and read about asp.net being bad and not supporting separation of layers! Who told you to include your business logic directly in the code-behind files? There are thousands and thousands of (official) tutorials on how to organize your code in layers using the App_Code folder and Web Services! We all know that .net for win applications (win forms) just didn't make it out and that Visual Studio and the whole .net team is focusing 100% on the web. So, cut the crap and let's talk about the real issue: why is microsoft publishing all these new technologies and features (linq, f#, mvc etc) in an inhumanly fast pace without considering the steep learning curve? I mean, come on, new things and options are a good thing but we all know what it feels like to eat your buffet meal in a hurry! My message to microsoft: let us digest the existing techniques; stop chasing competition. ruby for ruby people, php for php people and ASP.NET to us all (amen)!