CSLA .NET Version 3.0 Beta 2 is now available for download.
This is the final test release of version 3.0. Any changes between now and release will be bug fixes.
If you plan to upgrade please consider helping yourself and the community at large by downloading this version and testing it before July 5. Let me know about any issues through the forum.
CSLA .NET 3.0 provides support for Microsoft .NET 2.0 and 3.0.
If you want to build CSLA .NET 3.0 without .NET 3.0, you must define the NET20 symbol in the project properties.
CSLA .NET 3.0 includes enhancements useful to all 2.1.4 users, including these highlights:
· PropertyFriendlyName – specify a friendly name to use when displaying broken rule text
· Format – specify a format mask to use when displaying broken rule numeric values
· StringMinLength – new validation rule method
· DecoratedRuleArgs – useful for code generation of AddBusinessRules() methods
· Fix bug with stopProcessing and rule priorities
· RegEx – rule method now supports options for dealing with null values
· New CanExecuteMethod() functionality, similar to CanReadProperty() and CanWriteProperty()
Undo and Data binding
· If edit levels get out of sync an exception is thrown, making debugging of Windows Forms data binding much easier
· Cleaned up and rearranged interfaces to provide more consistency – making it easier to create UI frameworks on top of CSLA business layers
· Added TryParse() method
· Fix bug with CompareTo() method
SortedBindingList and FilteredBindingList
· Allow access to underlying source list
· Reworked data binding code to address all known issues
See the change log for a complete list of changes.
Of course the primary focus of CSLA .NET 3.0 is support for Microsoft .NET 3.0. Highlights include:
· WcfProxy – a data portal channel that uses WCF. You can transparently move from any existing data portal channel to WCF by using this new proxy.
· DataContract – support for using the WCF DataContract and DataMember attributes in your business classes
o CslaDataProvider – a data provider control that can create, fetch, save and cancel edits on a CSLA .NET business object. In some cases this can lead to code-less data entry forms!
o Validator – a control that provides Windows Forms ErrorProvider-like behavior to WPF forms that are data bound to CSLA .NET objects.
o Authorizer – a control that provides Windows Forms AuthorizeReadWrite-like behaviors to WPF forms that are data bound to CSLA .NET objects.
o ObjectStatus – a control that exposes IsValid, IsSavable and other properties from a CSLA .NET business object so they can be used by XAML data binding.
o IdentityConverter – a value converter that can be used to work around an issue with data binding and refreshing the UI.
· Added new WPF UI with equivalent functionality to PTWin.
· Added new Workflow UI to illustrate how a workflow can use CSLA .NET business objects
ProjectTracker\PTWcfClient and PTWcfService
· Added a WCF service illustrating how to expose CSLA .NET objects through WCF/SOA
· Added a WCF client app illustrating how to call a WCF service
· Added a WCF host for the data portal
Powered by: newtelligence dasBlog 2.0.7226.0
The opinions expressed herein are my own personal opinions and do not represent
my employer's view in any way.
© Copyright 2013, Marimer LLC