VS.NET Database Projects
I've decided to more or less punt on the MSBuildCommunityTasks issue; I'll provide the .MSI in source control, in a versioned folder, and allow/require devs to download and install in order to access the goodies contained therein.
Next steps: Database Projects! I have some sample code from another project I did that allows me to do a full, cool MSBuild-driven database build, from the schema on up. However, in porting to this new project (Cornbread), I realize that it is a lot of manual steps. Read that last part as "I realize that it is a very error-prone installation."
Some thoughts:
Provide a templated db project in VS.NET
Create an XML file that mirrors the required elements in the db project tree, and automatically check to make sure everything is there.
There's also a kludgey "shortcut" system I've developed to actually run the build. This requires some local batch files with the various verbosity parameters appended to the msbuild call. I would love to have this all integrated in my solution, and offhand I can't think of a reason why it couldn't be: emit the new .proj file from the solution, manually edit it, create a new configuration or two that calls the right targets, etc. Then, when you want to run your Database build, set the solution configuration to "Database Full Build" (or what have you), and Rebuild. You could link any number of steps, such as Compile -> Database Schema Only -> Unit Test -> Database Full Build in that manner.
Hm. I think I'll go down that path.
Next steps: Database Projects! I have some sample code from another project I did that allows me to do a full, cool MSBuild-driven database build, from the schema on up. However, in porting to this new project (Cornbread), I realize that it is a lot of manual steps. Read that last part as "I realize that it is a very error-prone installation."
Some thoughts:
Provide a templated db project in VS.NET
Create an XML file that mirrors the required elements in the db project tree, and automatically check to make sure everything is there.
There's also a kludgey "shortcut" system I've developed to actually run the build. This requires some local batch files with the various verbosity parameters appended to the msbuild call. I would love to have this all integrated in my solution, and offhand I can't think of a reason why it couldn't be: emit the new .proj file from the solution, manually edit it, create a new configuration or two that calls the right targets, etc. Then, when you want to run your Database build, set the solution configuration to "Database Full Build" (or what have you), and Rebuild. You could link any number of steps, such as Compile -> Database Schema Only -> Unit Test -> Database Full Build in that manner.
Hm. I think I'll go down that path.
posted by Anthony at 9:38 AM
0 Comments:
Post a Comment
<< Home