I can't wait to move to this.
I'm going to get to delete so much code.
Sorry, off-topic, but: Separated at birth? Below is a picture of Austrian radio host Peter L. Eppinger
ViewData vs. ViewModel... that's sort of unnecessary complexity to MVC. My vote is for ViewDataDictionary to inherit from IDynamicMetaObjectProvider so that we can have the best of both worlds with 1 concept. But that's just me....
Another great video. Love this more candid style.
Looking forward to trying out MVC 3
lol. Nice sense of humor.
Will my issue be solved in MVC3?
http://channel9.msdn.com/forums/TechOff/560601-ASPNET-MVC-MultiSelect-issue/
Dynamic Dictionaries are really easy to create in .NET 4, I did a post on it here: http://www.aaron-powell.com/dynamic-dictionaries-with-csharp-4 and although you do loose the intellisense capabilities I think that'd be a small price to pay to have a simplified data management method.
Having ViewData and ViewModel could get confusing (unless ViewModel is just a wrapper on ViewData) and it'd make testing harder as you need to ensure that the data is being added to the "right" collection.
that is good team. i know Phil Haack' blog and tutorials. i don't understand main goal of MVC 3. maybe my English is poor
Hey Now Scott,
Great Vid!
Thx 4 the info,
Catto