Is there a way to output a different namespace for the Adapter portion of the output? Also, would there be a way to only generate the data specific portion seperately in order to target multiple database types?

-Seth

Is there a way to output a different namespace for the Adapter portion of the output?

What do you mean by the Adapter portion of the output?

would there be a way to only generate the data specific portion seperately in order to target multiple database types?

Whenerver you re-genrate the code against a different database type using the Adapter model, a DBSpecific project is created to target that specific database.

As I understand it, the adapter scenario generates two different vs.net projects. One is database specific and the other is not. The goal is to re-use the non-db specific code across multiple database implementations. So I generally place the non-db specific code in a namespace that ends with .Data. I wanted to generate multiple db-specific projects to target multiple databases and have them exist in a namespace that has .Data.Sql or .Data.Ora etc. Since the non-db specific code does not have to be regenerated, I wanted to know if there was a way to only output the dbspecific code and change the namespace naming convention.

-Seth

I don't know of a way to only generate DBSpecific easily, but the generic project should always be the same so you should be able to export to the same folder for each project and then you will have one generic project and the mulitple DBSpecific.