-
4.5.Three < 4.5.Ten < 4.5.Twelve
-
Sounds like that's a management / team choice then - do you follow the existing pattern and process or is there a good reason to NOT use the existing pattern. Your choice - your decision.
-
Can you show an example? "We have a number of classes that provide business logic...." sounds like they might be candidates for being in your business layer model. If you wanted them to be CSLA inherited classes, what would they be? Command objects maybe? What are they actually doing in your user story?
-
Sounds like you are writing some ViewModels (i.e. that's the glue). I think there is a CslaViewModelBase class that helps here with binding - worth investigating.
-
I believe just version 4.3.13 supports Mono....at the moment.
-
Grid control could be firing BeginEdit's automatically - depends on the control, how you are using it, etc. Make sure when you do the save that you Unbind and Rebind to your data control.
-
This is one of those almost impossible questions to answer If you move to a WPF UI regardless if its SL or desktop, you will need new hardware and a graphics card to ensure that the UI rendering is fast. I had the unpleasant experience of having to deploy onto PC's with no graphics cards with WPF using software rendering and it was painfully slow
-
I notice in the ProjectTracker sample, the code does this in the MVC3UI project. ViewData.Model = ProjectList.GetProjectList(); return View(); Can we also return the model as a parameter in the View method? E.g. return View(theModel); Or is there some nuance with CSLA objects that means ViewData.Model is preferred. Or is this code a bit MVC 2 style
-
Your workaround is indeed the sort of thing you need to do. We had exact same problem with a Infragistics tab control which inherits from the MS one. WPF loads controls into the visual tree when they appear on the screen (sometimes you might be able to force them), but this can cause binding and validation issues. It's done for performance reasons
-
Sounds like it's a mix of .Net 3.5 and 4.0 here. I'd suggest try downloading verion 4.3.x of the framework and its samples, which has a later ProjectTracker sample. That all works in VS 2010 and .Net 4.