I was wondering if there was any material on upgrading from CSLA 2 to 4. I know that the code breaks somewhere around 3.5
Also I'm interested in the discussion on feasability/effort/scope/difficulty and also why we would do this. What sort of functionality or code structure changes could there be to warrant such an effort. What are the pros or positive effects on code performance/maintenance/ or generation. What sort of new features could be utilized.
The Using CSLA .NET 3.0 ebook discusses the benefits of CSLA 3.0. They center around support for .NET 3.0 features: WPF, WCF, WF.
However, CSLA .NET 3.0.5 is also the recommended version for .NET 2.0, because it includes a wide array of bug fixes and features around Windows Forms, and other .NET 2.0 scenarios.
So (imo) nobody should choose to run CSLA .NET 2.x anymore.
CSLA .NET 3.6-3.8 added support for Silverlight, ADO.NET Entity Framework and other .NET 3.5 and 3.5 SP1 features. This also includes support for ASP.NET MVC.
Starting in 3.6, code reduction was a major focus. So writing classes against 3.8 (current) means writing probably less than 50% of the code from early versions.
If you are using .NET 3.5 or Silverlight, you should use CSLA .NET 3.8.
If you are using .NET 4 or Silverlight 4, you should use CSLA 4, because CSLA 4 was created for this platform.
CSLA 4 also includes code reduction, and more abstraction around the data portal, and support for ASP.NET MVC 3.
What do you think about filling this out a little more and making a webpage that could easily show developers the evolution of the framework? Is there such a page already? I tried following the change log but it's hard to see the forest for the trees.
Copyright (c) Marimer LLC