I had SQL Source control version 0.3.1.3 working just fine. Then, I decided I needed to move the location of the SQL directory in the TFS (2005) repository. I disconnected SQL Source Control, then used the regular TFS manager to move the files to another location within my repository. I committed that move, then started SQL Source Control back up, and clicked "Link to a database already in source control". After I point the program to the correct (new) location for my source, I get a crash dialog box (which I did submit), and then a dialog box saying "Project file does not exist".
Attempting to get more information, I turned on some TFS network tracing, and I can see that SQL Source Control correctly creates a TFS workspace with the correct (new) directory, then pulls the change history for the RedGate.ssc file, which works successfully. That RedGate.ssc file has two revisions - the initial checkin that SQL Source Control made, and my move to a different location. The next thing that SQL Source Control does is attempt to pull all the files into the workspace. But when it does that, it doesn't pull the latest version - instead it pulls the old version (based on the original changeset of the RedGate.ssc file?). But the files were not in the specified directory at the time of that changeset, and therefore no files are downloaded. I presume the crash comes soon after that.
So, can you fix this issue, and how can I get my database reconnected?