I'm using the current latest version of LLBLGen Pro and have read many posts on architectural matters and on the merits, or not, of passing LLBLGen entities around.

Having already selected Adapter as the model most suitable for my requirements, and happy to pass the LLBLGen entities around, is it feasible to implement validation that uses something similar to Lhotka's broken Rules in my 'Manager' classes located in my BL?

The possibilites I see are:

1. Get access to the 'setter' for each entity field (is this possible?) in order to trap the Property Change event and so check for a broken rule.

2. Extend the Validation classes to check for a broken rule. Are these accessed every time an entity field changes?

3. Wrap the LLBLGen entities in order to set the fields bound to my UI and so get access to the Property Change event. This is the least favoured as it's a lot of work.

4. Move to the V2 beta now rather than later to make use of any better validation options there. I'm still getting to grips with LLBLGen and so it may make sense to acquire my knowledege with V2 rather than the existing, so it's a good option.

What do you think? All comments welcomed.

V2 validation methods are a big step in the right direction. Another approach could be to adopt Omar and Bashir's excellent JCL framework http://www.jclframework.net

Otis wrote:

V2 validation methods are a big step in the right direction. Another approach could be to adopt Omar and Bashir's excellent JCL framework http://www.jclframework.net

I had a look at JCL and am very interested, but because of timing, it's not fully oriented towards Net 2 so am looking forwards to JCL 2.

I have the impression that LLBLGen V2 will hit the streets by the end of June, is that likely?

Yes, that's our target date