Rockford Lhotka
    CTO at Magenic
    Author, speaker, software architect
    Creator of the CSLA .NET framework

Home
Blog
CSLA .NET
Magenic
Speaking
Publications
About me
Contact me

Login

Version 2.1.4 Change Log

 

2.1.4 Change Log

 

This document is the change log for version 2.1.4 of CSLA .NET.

 

Known issues:

CslaDataSource

When adding CslaDataSource to a page by choosing to “add a new data source” from within the GridView or DetailsView controls the data source control will not function properly in the designer, though it will appear on the page. (This appears to be due to a bug in Visual Studio in terms of how it loads the control into memory, and I’ve discussed it with Microsoft.)

The workaround is to switch the designer to Source view and back after adding the new CslaDataSource control to a page. This will force the designer to reload the control, making it act properly within the designer.

 

As before, you can add a CslaDataSource to the page by dragging it directly from the Toolbox, or by typing in the tag manually. Both of these techniques work immediately with no known issues.

 

Changes and Enhancements:

 

Csla\Web – CslaDataSource (070216)

Radical changes to the designer support for the control. The results of these changes mean that CslaDataSource now works with VS 2005 SP1, but also means that you can use classes in a web project or App_Code folder as data sources.

 

Csla\Web – CslaDataSource (070216)

Added a configuration dialog to make it easier to specify the business class that will be used as a data source. You can now click the Configure option on the control’s menu (or on the menu of any control bound to a CslaDataSource) to get this dialog.

 

Csla\Web – CslaDataSource (070222)

The TypeAssemblyName property is now optional. You have three choices:

  1. Use the separate TypeAssemblyName/TypeName properties
  2. Put all the information on TypeName and leave TypeAssemblyName blank
  3. Don’t provide any assembly name at all, only a type name

The new configuration dialog always opts for the second approach, and will convert your existing settings to this approach if you use the dialog.

 

The recommended approach is to set the TypeName field to a fully qualified type name (including the assembly), in the form <FullTypeName>,<AssemblyName>. For example: ProjectTracker.Library.Project, ProjectTracker.Library.

 

Csla – BusinessListBase (070220)

When a child item is removed, it is now removed from the active list first and then marked as deleted. That way when its OnUnknownPropertyChanged() method is called it doesn’t raise the event to the active list. This prevents an erroneous ListChanged (Reset) event from the list when removing a child. The change also affects the set operation, where a child is replaced by a new child, thus effectively removing the pre-existing child.

 

Csla\Validation – ValidationRules (070221)

Fix a bug where a null reference exception could be thrown when GetRuleDescriptions() is called on an object that has no per-type or per-instance rules.

 

 

(Updated 2/22/2007)