My previous post was about ASP.NET MVC 2, which no doubt people will use in combination with Csla.
But this one is more for Rocky to answer i guess.
Are there plans in supporting ASP.NET MVC 3 (currently in beta)
Also with using the "view engine" -> Razor
PS: Lots of support for dynamic language and dynamic data
I don't think MVC 3 will affect CSLA in any way, if anything the only thing I've seen so far is support IValidateObject (I just posted on this topic a day ago).
Razor is just a view engine, so that doesn't affect the model in any way. The dynamic properties added I believe are at the controller level, so again, nothing to do with Model.
wow... i always thought i was following technology, that is true for WPF and Silverlight
But as i was thinking/hoping Silverlight had a good future i kinda ignored ASP.NET webforms and ASP.NET MVC
wow.. in what i've missed what web technology has improved, i'm full in love with ASP.NET MVC
Using templates for MVC 2 i've found a nice blog from Brad Wilson (already over 1 year missed)
I think our new project isn't going to dynamicly create views at runtime, instead it's going to generate the controllers, models and views..
Our customers must have good tooling that will generate config and that config is going to be parsed to templates and more...
Maybe they can use webmatrix for a finishing touch...
Oh well 15.000 hours should be enough won't it :)
Anyway.. To continue my question...
I'm intrested to discuss with other developers who are or who are going to use ASP.NET MVC 3 as frontend using csla business objects as the ObjectModel behind the ViewModel (for extending the ObjectModel with for example frontend commands)
For who has time to play, yesterday the Releae Candidate shipped
Rocky, is your strategy supporting ASP.NET MVC 3 ?
There is for example an dynamic ViewModel property in the ControllerBase in which an model implimenting IViewModel could be set.
Yes, I'll be looking at MVC 3 to see if there are things CSLA can do to better support the technology.
It is important to remember though, that CSLA is a business layer technology - it helps you create the Model in MVC, MVVM, etc.
This often means that new revisions of a UI technology have little impact on CSLA itself. Unless they invent a new data binding technology, or a new scheme by which model objects are instantiated, there's usually not a lot that needs to be done.
MVC 3 is backward compatible with MVC 2, so all the nice functionality in Csla.Web.Mvc should continue to work nicely with MVC 3.
Right now my priorities are around CSLA 4 verison 4.1 (WP7 support) and getting the related ebooks done.
Copyright (c) Marimer LLC