Hi,

Now, i'm intended to use LLBLGen for all DB we use here (4).

If I create one project for each DB, i will end up with 8 project (and DLL), plus my own libraries.

Has anyone tried to put DatabaseGeneric and DatabaseSpecific together on the same project (Adapter)? If it is possible, I will have only 4 DLLs, one for each DB. Cool!

Thank you,

David

You only need one dbgeneric for all 4 db's, and one dbspecific per db. That is, if the entities are all the same of course (though that's what I expect, otherwise you'll have 4 different apps as well ).

So because the entities look the same for all db's, you can share one dbgeneric for all 4 db's, that's the reason the projects are split up

Oh... sorry... I didn't explain it right...

All these 4 DB are completely different DB (Telephony, CRM, Product1, Product2).

Although, in the begging, the separation in 2 DLLs was not a problem, now it can be a little bit confuse if I use LLBLGen for all these DB.

In the end, I'd like to have something like this:

MyCompany.Data.Telephony.dll (DatabaseGeneric + DatabaseSpecific) MyCompany.Data.CRM.dll (DatabaseGeneric + DatabaseSpecific) MyCompany.Data.Product1.dll (DatabaseGeneric + DatabaseSpecific) MyCompany.Data.Product2.dll (DatabaseGeneric + DatabaseSpecific)

Am I missing something?

I don't see a way to do this currently as 2 projects and still maintain the kind of namespaces that you want. The only thing I could suggest is that you use ILMerge to combine your assemblies together after they have been created:

http://www.microsoft.com/downloads/details.aspx?FamilyID=22914587-b4ad-4eae-87cf-b14ae6a939b0&displaylang=en

I've not used the tool myself so I can't vouch for it personally, though I've often considered it to ease some deployment scenarios.

You can of course simply add the files of the dbspecific project to the dbgeneric project, and be done with it.

Otis wrote:

You can of course simply add the files of the dbspecific project to the dbgeneric project, and be done with it.

I gonna try. Thanks.