can we use auditor object for exception handling, if yes how to consume the corresponding auditor object, if the exception occurs in the validator or any other related object

I want to scope all of these to use MerchandiseConsumerAuditor.

ConsumerEntity MerchandiseConsumerValidator MerchandiseConsumerAuthorizer

Or should I go the route of using log4net or enterprise log application block?

The auditor can only handle the following actions:

1- Setting a field value. 2- De-referencing a related entity. 3- Referencing a related entity. 4- Saving a new entity. 5- Updating an existing entity. 6- Deleting an entity. 7- Getting a field value. 8- Loading an entity.

can we use auditor object for exception handling

So, the answer is no.

I don't know if I put the question correctly. Can we use Auditor for logging including exceptions? If no, how to plugin the log4net object as a dependency object

thanks

Hi Vairam,

LLBLGenPro Validation feature don't listen for exceptions to be trapped and logged. You should be that is some place, for example catch your involved exception at some point (BLL, GUI, etc.) and log it manually using some validation extension code.

So LLBLGen is about Entities, no exceptions. Even if you use log4net you should at some point catch the exception and log it.