Windows Form Tool for Managing Migrations

[GoogleCodeExporter]

I'm not sure if I am using the framework differently from others, but I've
built a tool that leverages the framework and can contribute it if there is
interest.  Here's why I wanted it:

I am doing a lot of work where I am using PLINQO to generate my business
entities.  For this reason, moving migrations up and down a lot is a
natural occurrence while I tweak my entities.  But, I also have an
application where I have multiple databases, and the adding external tools
works ok for a single database, but when you have 4, well, it's not good. 
Lastly, I have build configurations for dev and test so that I can run unit
tests against a separate instance of my database.  Of course, I am still
using the normal build aspects in my build file, but I wanted a way to work
with the framework during the natural development cycle.

So, what I built is a Windows app that lets you have a configuration file
for multiple configuration entries.  The file can be saved with the
solution so you can easily switch between apps you are working on (and it
has a MRU list so you don't have to keep browsing to them).  It does not do
anything with the registry, so no installation is required (the MRU is a
simple serialization to XML in the directory of the app).  It also shows
all the migrations in an assembly configuration, so you can select a row
and migrate up/down to that version.  It will run the Migrator Schema
dumper or (and I was a bit lazy here) you can get a rough current schema if
it is a SqlServer provider.  And lastly, you can migrate all the way down
or up with a single click.  

I'm sure it's a little rugged, but I'm using it now, and the only problem I
have is that I can't get the app to release the assembly from the Migrator
instance, so you have to close and re-open the app.  However, since it
opens the most recent file, it's not that bad.

I'll probably do a little more tweaking on it, but if you are interested, I
can post the source as a zip and maybe it could be added to the contrib
project.

I'm also curious if other people are using the framework in this way...

Original issue reported on code.google.com by spencer....@gmail.com on 2 Sep 2008 at 5:57

[GoogleCodeExporter]

Oops -- that was supposed to be an enhancement, not a defect.  Sorry about that.

Original comment by spencer....@gmail.com on 2 Sep 2008 at 5:58

[GoogleCodeExporter]

This probably won't get done anytime soon unless someone decides to contribute 
a 
patch.

Original comment by geoffl...@gmail.com on 5 Sep 2008 at 9:28

• Added labels: Milestone-Later, Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I can release the tool we're using internally soon. We're just re-factoring the
interface right now. Not a top priority for us ATM, but I can submit a patch 
when
it's complete. Poke me if you don't hear from me in a month, I tend to forget 
these
sorts of things.

Original comment by james.sa...@gmail.com on 8 Mar 2009 at 9:27