Does anyone know if its possible to have the two generated projects output the code to different folders? The way I have this setup now is to have the two projects added to vs.net 2003 individually, but when I view the projects in vs.net I see the other project in the folder as non-included files. What I would like to do is split the projects into independent filders. Any idea's would be appreciated.

See project properties, task performers section. You can there specify the folders to which you want to generate the dbspecific/dbgeneric code. Is that what you're asking, or do you want more fine-grained split up?

Otis wrote:

See project properties, task performers section. You can there specify the folders to which you want to generate the dbspecific/dbgeneric code. Is that what you're asking, or do you want more fine-grained split up?

This is what I was asking, though if there was a more fine-grained way of splitting up the classes it would be very helpful to me. I tend to have a lot of classes that I would group together by domain. I would love to have some classes get generated into a Product namespace/folder and others go into a Order namespace/folder. Is this sort of thing possible?

Otis wrote:

See project properties, task performers section. You can there specify the folders to which you want to generate the dbspecific/dbgeneric code. Is that what you're asking, or do you want more fine-grained split up?

I'm looking at what you suggested and I don't think the "Project Properties/Task Performers" is going to do what I want. I say this because I think it's the "Project/Generate F7" screen that sets where the code is generated. At the bottom there is a "Destination root folder" and this is where both projects get generated. This will also place both project files and their subfolders into the same root. I would expect that this is where two different project locations would be set if it was possible. Is this correct?

Project properties is used to establish defaults. Project Generate lets you override the defaults.

Paul.Lewis wrote:

Project properties is used to establish defaults. Project Generate lets you override the defaults.

Though I think what he means is that the root folder specified in the generator config dialog is just 1. Say you want the dbgeneric project in C:\myprojects\Foo and the dbspecific project in C:\somefolder\bla, you can't, you have to generate twice.

Otis wrote:

Paul.Lewis wrote:

Project properties is used to establish defaults. Project Generate lets you override the defaults.

Though I think what he means is that the root folder specified in the generator config dialog is just 1. Say you want the dbgeneric project in C:\myprojects\Foo and the dbspecific project in C:\somefolder\bla, you can't, you have to generate twice.

Yeah, this is exactly what I mean. I want to generate the two projects into their own folders.

For now, generate two times. To make things easier, make 2 copies of the adapter generator config you want to use, and in one you strip out all the tasks for the dbgeneric project and in the other the tasks for the dbspecific project. (be sure to alter the name tag contents)

Then you create a small .cmd file (bat file) and use the command line generator to generate the project two times, first the dbgeneric one, using the copy of the generator config with no dbspecific tasks) and then the dbspecific one. It's perhaps a bit cumbersome, but it's the easiest it can get at the moment, as the generator config dialog works with one root folder.

OK, thanks Otis. I can do this, but will you provide this option in the designer in the future?

Yes