LLBL Pro version = 2.5 final runtime version = v2.0.50727 Using ASP.NET 2.0 Database = MS SQL 2005 selfsevicing

Hi,

Sorry if this is a basic question but I'm new to LLBlGen Pro and after searching the formus and faq's I can't find any satisfactory answers.

I'd would like to find out what's the best way to initialize a property of a newly created entity? I think that it should go in InitClassEmpty() method before the call to InitClassMembers(). The problem is everytime i regenerate the LLBLGen project I loose the code I've added to the InitClassEmpty() method. Can I move the //__LLBLGENPRO_USER_CODE_REGION tags up so my code will initialize my properties before the call to InitClassMemebers(). Everytime I move the user code region tags and regenerate the project the generated code is all messed up.

Please advise

Why do you want to put your code exactly before InitClassMember()?

Anyway, while you can't move the USER_CODE_REGIONS, there are various options in your case:

• Override OnInitialized method in a partial class and put your code there (you can check if this.IsNew to know if the entity indeed is new.

• Override InitClassEmpty in a partial class and put your code there.

I have an audit trail class that overrides the AuditEntityFieldSet method to capture the fields that are being changed. The fields I need to initialize when a new entity is instantiated are not suppose to get audited, so if I initialize the fields before the the call to InitClassMember() the AuditEntityFieldSet event will never get firedcand my audit trail class will not be capturing those fields I have initialized upon enity instantiation. Is there another way to accomplish the above? Am I making sense

If you want to ignore fields being audited, why don't you grab the auditor in the init method, set a property to ignore audits from then on, set the fields, and reset the flag ? In the auditEntityfieldset method you then test the flag and if its' true ignore the audit call, otherwise audit the call.

Thanks Otis and David,

I think Otis' solution will work best in my situation. I will be able to place my code in the between the user code region tags in the enitity class directly.