Tuesday, January 15, 2008
« January's Magenic webinars (including on... | Main | Why so few WPF/XAML grid controls? »

I have refreshed the CSLA .NET 3.5 download with much more recent code. (www.lhotka.net/cslanet/download.aspx)

The C# and VB versions of the framework and ProjectTracker are now very comparable. The only difference is that the VB framework doesn't have the LINQ extensions yet (though the C# version doesn't have the coolest parts yet either).

Some highlights:

  1. All the new property/field/child management code is in both versions. The result is code reduction of ~35% per property and no more string literals for property names.
  2. All the new child object code is in both versions. The result is no more plumbing code for child objects, "automatic" lazy loading support and consistent persistence for root and child objects.
  3. Both versions have seriously enhanced type coercion that is used by the new property scheme and by DataMapper.
  4. Both versions have much improved type casting for SmartDate, allowing much more flexible use of this type.
  5. Check out the new ConnectionManager and ContextManager classes in Csla.Data for simplification of data access code with ADO.NET or LINQ.
  6. ProjectTracker.Library now uses an external data access assembly, which was created using LINQ to SQL.

There are many other changes/enhancements/fixes - check out the change log for details. Or look at all the green items in the wish list, because that's all in 3.5.

I am still planning to do a beta release around January 25, so this is probably the last preview release before the beta.

I'm still working on a number of issues, and have more testing to do in general, but this is getting reasonably close to the final 3.5 feature set.

If you have comments/questions/concerns, please voice them now! Once the beta starts I'll be doing bug fixes only.


Wednesday, January 16, 2008 6:01:26 PM (Central Standard Time, UTC-06:00)
Rocky, has there or will there be any serious testing in regards to performance and object graph size due to new property management? It would be interesting and I think beneficial if someone like Magenic does this type of testing. Would probably be helpful to folks who are interested in csla 3.5 but may wait until it is clear what performance issues may be involved with upgrading.

BZ
Friday, January 18, 2008 9:57:51 AM (Central Standard Time, UTC-06:00)
I've done some perf testing, and will continue to do more. I'm leery of publishing the perf results because I worry people will take them as a "definitive answer".

But CSLA .NET is so incredibly flexible (intentionally) in terms of how it can be used, that any perf tests tend to be at the mercy of specific implementation choices and environmental scenarios that may or may not match YOUR chocies/scenarios...

In this case I'm doing some low-level testing though, which doesn't vary by scenario (speed of reflection-based method calls, etc) and so I may publish some of these results because they probably ARE definitive :)
Friday, January 25, 2008 10:39:07 AM (Central Standard Time, UTC-06:00)
Rocky,

The addition of automatic lazy loading sounds great! I've never used lazy loading in the past but there are usually a few places in an application where it would be handy to have. Usually, I just end up creating to versions of the business object. A simple one without children that is editable and the full-blown one with all of the children objects. I like the idea of putting those back into one BO and having the ability to lazy loading. Thanks!

Jon
Jonathan Miller
Comments are closed.