I would like to know whether LLBGen Pro can be integrated into a code base of existing business data classes and existing database tables. I cannot modify my current business data classes or database tables in any way. Many of these business data objects are grouped into generic or custom collections.

I can pass my collections of business data objects to any new classes needed to create, update, and delete records in the database for the data exposed by the public properties of my business data classes.

I want to know if this possible using LLBGen Pro?

I can't see why this would be a problem. In this case you need to think of LLBLGen as very much a Data Access layer, rather than focusing on all the other functionality the LLBLGen provides (serialisation, field level roll backs, entity change tracking,data binding etc etc etc... ).

In effect you would need to provide a translation layer between your data objects and the LLBLGen objects.

What about your existing setup is prompting you to change - perhaps we can help further ?

Matt

Yes, I want to use LLBLGen to generate the data access layer, not the business data layer.

What would the translation layer consist of? A set of objects that would populate my data objects using LLBLGen objects?

We are in the middle of creating a brand new application in VB.NET, but we don't want our tools to dictate the architecture. The business data layer must be vendor-neutral.

Thanks,

Norm

With regards to my post on 29-Jan-2010, would I have to create a set of classes that would populate my data objects using LLBLGen objects? Would that be one new class for each LLBLGen object?

Please advise.

Norm

How you architect this would be entirly up to you, there are no "correct" answers. At the least you need to find some way to map your data objects to LLBLGen objects, and back again.

LLBLGen provides several features that could make this simpler for you. As you have access to the templates used for code generation is usually a simple matter to extend/modify these to generate extra code, for example mapping routines, and possibly even your LLBLGen independent domain objects - depending on how closely they map to the database.

LLBLGen objects are also completly serializable to and from XML - you could use this to assist in translating between our objects and your own.

Matt