CslaContrib and Csla4

Posts 1,770

Reply

JonnyBee Posted: Thu, Dec 30 2010 8:07 AM

rated by 0 users

Hi all,

I'd like to remind everyone of the CslaContrib project at http://cslacontrib.codeplex.com and wish to welcome contributions for Csla4.

Already available are:

CslaContrib
* Caching capabilities in DataPortal with Windows Server AppFabric (courtesy of Magenic)
* Additional generic rules like: LessThan, LessThanOrEqual, GreaterThan, GreaterThanOrEqual, ToLowerCase, ToUpperCase and more.

CslaContrib.MEF
* MEF support with intermediate base classes for Repository data access
* Custom ObjectFactoryLoader and ObjectFactory attribute for ObjectFactory data access

CslaContrib.Windows with updated controls for Csla4
* ErrorWarnInfoProvider
* SmartDateTimePicker
* BindingSourceExtension (Unbind/Rebind)
* BindableRadioButtons
* ListSelectForm
* SplashPanel
* StatusStripExtender

As well as sample code for using MEF with both Repository and ObjectFactory data access.

The previous content for older versions of Csla is still available in the $\Brances folder.

I'm sure many of you have code and samples that you could consider to share with the community. If you wish to contribute then contact me on the CslaContrib site.

You may send me code (with grants to publis it on CslaContrib) or I can give you contributor access to CslaContrib.

Jonny Bekkum, Norway CslaContrib Coordinator

Posts 450

Reply

Tiago Freitas Leal replied on Fri, Dec 31 2010 7:45 AM

rated by 0 users

I'm glad to see CSLAcontrib back in action. Besides CslaComboBox (ComboBox with a read only behaviour) that is already in the trunk, i intend to submit SmartDate improvements for Csla 4. As to CslaActionExtender improvements (http://forums.lhotka.net/forums/p/8009/38445.aspx) I'm not sure if they should be done in Csla trunk or CSLAContrib. A few Transformation Rules are also on the pipeline.

I use a "customized" CustomIdentity / CustomPrincipal that were extended to support extensive authentication information like WindowsIdentityAuthenticationType (NTLM, LDAP, etc) LocalStatus, LocalMachine and LocalDomain names, current Windows authenticated user and current Csla authenticated user (they can be different) and also Csla UserID. I'm willing to share this but as it uses some of Rocky's code from PTracker, I'm not sure if both licenses are compatible.

I'd like to see CustomFieldData ported to Csla4.

These look a lot like a new year's decision, but that's just a coincidence Smile

Tiago Freitas Leal, CslaGenFork (Open Source CSLA code generator)

Posts 1,770

Reply

JonnyBee replied on Mon, Jan 3 2011 8:50 AM

rated by 0 users

Hi Tiago,

I'd probably regard LocalStatus, LocalMachine, LocalDomain names, current Windows authenticated user etc to be contextual information and rather put these into ApplicationContext.ClientContext (and will be submittet on every to call to the server) rather than viewing it as authentication information and part of the Indentity/Principal object. Just my opinion - both ways work but having it as contextual information would work with any type of authentication. Geeked

CustomFieldData is "ported" by Jason Bock to Csla4 and available here:
http://jasonbock.net/JB/Default.aspx?blog=entry.9cc70d85bef34e2b9a683ba82615f8a3

Jonny Bekkum, Norway CslaContrib Coordinator

Posts 450

Reply

Tiago Freitas Leal replied on Sat, Jan 8 2011 1:38 PM

rated by 0 users

JonnyBee:

I'd probably regard LocalStatus, LocalMachine, LocalDomain names, current Windows authenticated user etc to be contextual information and rather put these into ApplicationContext.ClientContext (and will be submittet on every to call to the server) rather than viewing it as authentication information and part of the Indentity/Principal object. Just my opinion - both ways work but having it as contextual information would work with any type of authentication.

Funny enough, that's exactly what I do. On successful login, i call

private static void SetContext()
{
    ApplicationContext.ClientContext["LocalStatus"] = NetworkInformation.LocalComputer.Status.ToString();
    ApplicationContext.ClientContext["LocalDomain"] = NetworkInformation.LocalComputer.DomainName;
    ApplicationContext.ClientContext["LocalMachine"] = Environment.MachineName;
}

Wink

Tiago Freitas Leal, CslaGenFork (Open Source CSLA code generator)

Posts 184

Reply

Blake Niemyjski replied on Tue, Jan 18 2011 12:53 AM

rated by 0 users

Hello,

Are the SmartDate's and Smart Datatypes even relevant anymore? Nullable types replace the behavior and it is built in to .NET. Not using them sure makes the DAL much easier to program against.

Thanks

-Blake Niemyjski

Thanks

-Blake Niemyjski (Author of the CodeSmith CSLA templates and CSLA Core team member).

Posts 1

Reply

uiopasa replied on Tue, Jan 18 2011 4:08 AM

rated by 0 users

I implemented the example described in Rocky's MVVM video "Deeper dive into collections". I was succesful in my implementation of the "New Employee" and then went forward to implement his navigation example going from the list of employees to the employee item. The navigation works fine (I get my list and can edit the selected item) but for some reason, when I click on my button to create a single item, the propertystatus controls will not validate my object anymore and therefore will not change the status of my fields and buttons. Any help would be greatly appreciated.
Pure Collagen Skin Care