Namespace How-To Question

Posts   
 
    
can1
User
Posts: 77
Joined: 16-Sep-2005
# Posted on: 04-Nov-2005 15:39:55   

Hello,

I am using the extended adapter templates. I would like to generate my database generic code into the CompanyName.Product.BL.Entities namespace and the database specific coding into the CompanyName.Product.BL.DAO namespace.

I can't figure out how to do it through the project properties? There is a root namespace property and a database specific suffix property, meaning that the database specific namespace must always be a sub-namespace of the database generic namespace, ie. CompanyName.Product.BL.Entities and CompanyName.Product.BL.Entities.DAO ?

Is there any way to have the db generic and db specific namespaces at the same level: CompanyName.Product.BL.Entities and CompanyName.Product.BL.DAO ?

Thanks,

Can1

Paul.Lewis
User
Posts: 147
Joined: 22-Aug-2005
# Posted on: 05-Nov-2005 04:15:34   

This thread offers one solution to meet your namespace desires.

http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=2103

An more direct solution isn't available at this time.

Answer
User
Posts: 363
Joined: 28-Jun-2004
# Posted on: 05-Nov-2005 19:11:19   

I have a need for this same thing. I hate using cmd line stuff rage

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39933
Joined: 17-Aug-2003
# Posted on: 06-Nov-2005 11:25:34   

Project properties -> Task performers section -> AdapterDbGeneric and AdapterDbSpecific namespace suffix, change to a different value.

Frans Bouma | Lead developer LLBLGen Pro
can1
User
Posts: 77
Joined: 16-Sep-2005
# Posted on: 16-Nov-2005 16:44:38   

There is no AdapterGenericNamespaceSuffix, only an AdapterDbSpecficiNamespaceSuffix.

So, all db specific namespaces, must always be a sub namespace of of the generic namespace?

Can1

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39933
Joined: 17-Aug-2003
# Posted on: 17-Nov-2005 10:13:30   

can1 wrote:

There is no AdapterGenericNamespaceSuffix, only an AdapterDbSpecficiNamespaceSuffix.

So, all db specific namespaces, must always be a sub namespace of of the generic namespace? Can1

That's indeed an oversight in the current codebase and my mistake in suggesting that this option is available.

This doesn't have to be that bad. The idea is that code is generated for the generic project once, and then code is generated for the db specific side, and if you support more than one database type, the db generic project for other databases is not used anyway.

Frans Bouma | Lead developer LLBLGen Pro