CSLA .NET 3.8 Beta 1 is available

CSLA .NET 3.8 Beta 1 is available

Old forum URL: forums.lhotka.net/forums/t/7732.aspx


RockfordLhotka posted on Tuesday, October 06, 2009

CSLA .NET version 3.8 Beta 1 is now available for download.

Beta 1 brings the WPF PropertyStatus in line with the Silverlight version.

And Beta 1 adds support for the System.ComponentModel.DataAnnotations attributes. Data annotation attributes applied to properties are automatically added as rules using the CSLA .NET validation rules subsystem when ValidationRules.AddAnnotations() is called in your AddBusinessRules() override. If you don’t override AddBusinessRules() the base implementation calls AddAnnotations() on your behalf.

The C# ProjectTracker has been updated to work with 3.8.

I am pretty happy with the changes I've made to the various XAML controls - even though there are some breaking changes with PropertyStatus and InvokeMethod.

The result is good support for MVVM in WPF and Silverlight, with consistency between the two (I've even been able to copy-paste XAML between WPF and SL projects).

The MVVMexample projects in samples (for .NET and SL) show the basic capabilities added in 3.8, and ProjectTracker (C#) and InventoryDemo (SL) have been updated without incorporating MVVM. I may change InventoryDemo to use MVVM though, as it would simplify the application I think.

In any case, this is a beta release because I think I'm about done. I'll let Beta 1 float for a couple weeks to see if you find any issues with the design or implementation of the new features. Then I'll do a Beta 2 for stabilization and then release.

So I expect 3.8 to release in early November. If you use WPF or Silverlight, please take the time to look at 3.8 and give me feedback now. Feedback is always welcome, but is obviously far, far more useful right now than 4 weeks from now :)

Jack replied on Wednesday, October 07, 2009

Rocky,

I am having some issue with deploying 3.8b1 and the System.ComponentModel.DataAnnotations.dll.  I'm not sure if CSLA is bundled with an older version or where I need to be referencing it so it is deployed correctly.

What is interesting is I am seeing different behavior and errors depending on the server / browser.  For example in SilverlightSpy (which I thought piggybagged on IE) I get lots of errors but at the same site using IE I have no issues.

I had a comment from another user who saw the error once but never again. (looks like this one:

http://www.screencast.com/users/JackAddington/folders/Snagit/media/71af61aa-dacc-4860-953d-0a5e25afa4b3

The big ugly exception is here:
http://screencast.com/t/BSxkpXy6E



thanks

jack

Jack replied on Wednesday, October 07, 2009

I think I found the issue - This webserver only had the .net 3.5 not 3.5SP1.  I'm removing the references from my app and that should fix the problem.  I'll post again if I have any issues.

 

From: Jack [mailto:cslanet@lhotka.net]
Sent: October-07-09 9:03 PM
To: jaddington@alexandergracie.com
Subject: Re: [CSLA .NET] CSLA .NET 3.8 Beta 1 is available

 

Rocky,

I am having some issue with deploying 3.8b1 and the System.ComponentModel.DataAnnotations.dll.  I'm not sure if CSLA is bundled with an older version or where I need to be referencing it so it is deployed correctly.

What is interesting is I am seeing different behavior and errors depending on the server / browser.  For example in SilverlightSpy (which I thought piggybagged on IE) I get lots of errors but at the same site using IE I have no issues.

I had a comment from another user who saw the error once but never again. (looks like this one:

http://www.screencast.com/users/JackAddington/folders/Snagit/media/71af61aa-dacc-4860-953d-0a5e25afa4b3

The big ugly exception is here:
http://screencast.com/t/BSxkpXy6E


Error! Filename not specified.Error! Filename not specified.
thanks

jack


JimStone replied on Tuesday, October 13, 2009

An issue with the DataAnnotations attributes in Silverlight.

It believe that I should be able to apply multiple of these. (I can when using a DataForm) For example  <Required> and <RegularExpression> together on one property to ensure a valid entry is made.  

However, while CSLA will add two, and check two, if the second one passes, then the first one is deleted from the brokenrules list.   (Because they both have the same name?)

This ability to have two is quite necessary since, as documented on msdn, an empty test string will always pass validation based on the RegularExpressionAttribute.

RockfordLhotka replied on Tuesday, October 13, 2009

Good catch, thanks!

Copyright (c) Marimer LLC