Instead of

private static SimpleRule firstNameRule;
static CustomerModel()
{

firstNameRule = new SimpleRule(”DataValue”, “Firstname can not be empty”,
(Object domainObject)=>
{
DataWrapper obj = (DataWrapper)domainObject;
return String.IsNullOrEmpty(obj.DataValue);
});
}

use:

private static SimpleRule firstNameRule = new SimpleRule(”DataValue”, “Firstname can not be empty”,
(Object domainObject) =>
{
DataWrapper obj = (DataWrapper)domainObject;
return String.IsNullOrEmpty(obj.DataValue);
});

This way, as FxCop says, you can get rid of the Static Constructor and instantiate the SimpleRule in the very same moment you declare it, gaining some performance improvement.
Appears reasonable to me. Do you think is a proper thing to do?
Best regards.
Roberto
BTW did you become a father already?
In a couple of weeks I’ll have my third boy.

As I commented on CodePlex, I’ve found your Cinch and documentation to be most helpful. However, I’m trying to take some elements of Prism and use some of the things in Cinch and mix and Match.

My mindset has been to focus on modules and in your sames, you use your own display methods.

I tried to find your contact info but haven’t had any success.

At anypoint, I’m going to start new assembly and pick and match things I find useful. Much of what you claim to have done with Cinch.

But I wanted to let you now before I got started into it.

Thanks.

I’m very happy the framework made it into Cinch – given Cinch is really quite awesome, this might get our little façade quite a boost. Hope SLF will serve you well