search

minhphien / migratordotnet

Automatically exported from code.google.com/p/migratordotnet
0 stars 0 forks source link

Web front to run migrations #40

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
It would be nice to have a web front end to use migrations for those of us
stuck using a shared hosting account.  When it is not possible to use a
build tool to run our data migrations and have no access to the command
line.  Nothing to complex, like maybe a button to run up and and a button
to run down.

Original issue reported on code.google.com by ccp.ch...@gmail.com on 30 Jun 2008 at 7:08

GoogleCodeExporter commented 9 years ago 
interesting request.

we would have to just make a new implementation that matches that of 
Migrator.NAnt 
to run the migrations manually passing along the migration you want to go to.

I suppose this wouldn't be too difficult.

Original comment by dko...@gmail.com on 30 Jun 2008 at 7:56

GoogleCodeExporter commented 9 years ago 
Attached is a patch to add a very basic Web Runner.  Build script hasn't been 
updated
to make it nicely yet.  It'll show you the current version and a dropdown of 
versions
to choose from for your migration.  Not beautiful, but it works.  You'll want to
configure connect strings etc. and add some security in web.config.

Original comment by evon...@gmail.com on 26 Jul 2008 at 8:13

Attachments:

GoogleCodeExporter commented 9 years ago 
And attached is a patch to get the build script to compile it.  Winds up in 
build/web.

Original comment by evon...@gmail.com on 26 Jul 2008 at 9:03

Attachments:

GoogleCodeExporter commented 9 years ago 
cool deal.

i had a hdd failure yesterday so I am re-installing vs2005 now. I will apply 
this 
patch later this afternoon. thanks!

Sean

Original comment by dko...@gmail.com on 27 Jul 2008 at 2:00

GoogleCodeExporter commented 9 years ago 
can you post the add-web-runner patch again. there seems to be a problem with 
the 
patch file.

Original comment by dko...@gmail.com on 31 Jul 2008 at 2:50

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Regenerated the patch again, against v103 and with the build script changes 
too.  The
deleted patch from comment 6 was missing the web.config and project files.

Original comment by evon...@gmail.com on 31 Jul 2008 at 3:12

Attachments:

GoogleCodeExporter commented 9 years ago 
I am still having a problem applying the patch, when i attempt to load the file 
to 
patch i get "The patch seems outdated! the patchline and the file line do not 
match"

This is on the Migrator.sln file which is showing a conflict. All the other 
files 
seem to work fine. Ideas?

Original comment by dko...@gmail.com on 31 Jul 2008 at 4:09

GoogleCodeExporter commented 9 years ago 
It looks like TortoiseSVN is having a major problem with the unicode characters 
at
the front of Migrator.sln.  I'm using 1.5.2 now to make the patch - and if I 
create
patch, revert, then apply patch I get the same error.  I also tried converting 
the
patch to unicode and then applying it - no dice.

I will see if I can use a different tool to create the patchfile.  Or, I can 
create a
patch for everything but the .sln and send you the new sln separately.

Original comment by evon...@gmail.com on 1 Aug 2008 at 12:55

GoogleCodeExporter commented 9 years ago 
I tried stripping the unicode header from my sln file and regenerating the 
patch and
that seems to make Tortoise happy.  Try this patch out, if you wouldn't mind.

Original comment by evon...@gmail.com on 1 Aug 2008 at 1:00

Attachments:

GoogleCodeExporter commented 9 years ago 
This might make sense to go into a "contribs" type system as it's sort of 
outside of the normal usage pattern. Not 
saying it's not interesting - just seems like a special case?

Original comment by geoffl...@gmail.com on 1 Aug 2008 at 2:50

GoogleCodeExporter commented 9 years ago 
I'll move my code into a new /contrib/Migrator.Web and provide a new patch if 
you'd
like.  Should the main build script still compile it, or should it have its own
script?  How do you want it packaged - I assume as a separate zip file?

Original comment by evon...@gmail.com on 4 Aug 2008 at 1:57

GoogleCodeExporter commented 9 years ago 
The directory choice is fine. Let's have a build script under contrib for those 
guys.
If you get ambitious, then go ahead and have the script create a zip file as 
well. We
can always tie together the main and the contrib with a 3rd script if need be.

Original comment by geoffl...@gmail.com on 4 Aug 2008 at 2:20

GoogleCodeExporter commented 9 years ago 
Attached is a new patch that moves the web frontend into contrib/ and adds a
buildscript for it.  I also moved the web frontend project into a new group 
called
contrib in the solution file.

Original comment by evon...@gmail.com on 5 Aug 2008 at 3:05

Attachments:

GoogleCodeExporter commented 9 years ago 
SVN 112
Applied the patch with a few minor changes. 
Left it out of the main Solution file for now. We might want to create a 
solution for
the contrib projects if we get more of them.

Thanks evonzee!

Original comment by geoffl...@gmail.com on 5 Aug 2008 at 10:40