Is there a way to generate a single DatabaseSpecific project that will work against several DatabaseGeneric projects?
A client wishes to generate portions of a schema into a single "common" project for all shared tables and a separate project for each portion of the schema that is stand-alone. The idea being that if a stand alone library needs refreshed for one application, one would not need to refresh libraries in every application corporate wide.
If I create a project that includes the complete schema, then create a new project for each sub schema and replaced the DatabaseSpecific projects from the "sub schema projects" with the DatabaseSpecific project from the "complete schema project" would it work?
Seems like it should from a high level, but am I opening up a can of worms when it comes to maintaining it? Also can you tell the generator not to generate the DatabaseSpecific project? That would reduce the amount of code to discard and eliminate the possibility of the wrong DBSpecific project getting into the solution...
Any thoughts?