Feb 22, 2012 at 4:20 PM
Edited Feb 22, 2012 at 4:21 PM
I've been using VssMigrate 0.2.0.0 to move a few projects. It hasn't always been smooth sailing but the problems I've been faced with have been solvable. I'm grateful to the developers who have contributed to this project. I'm especially fond of the
feature that groups individual check-ins into changesets.
With that being said, I'd like to propose a couple of improvements.
- Validate configuration settings before starting the migration process.
When I first started using VssMigrate, I tested it on a relatively large solution. The 'scanning' phase took maybe 30 minutes. Only when VssMigrate entered subsequent phases, in which it attempts to communicate with the SVN server, did it become apparent that
my app.config settings were incorrect. I think it could save novice users a lot of grief if a 'validation' phase were placed at the beginning in which the app.config settings would be verified.
- Add option to generate a dump file
Maybe this is a stupid idea, but it seems to me that the complexity involved in getting the history correct in SVN could be reduced by generating a dump file and then using svnadmin load to load it into the repository.