File content mash-up
Hello,
We're just about to migrate to TeamSystem from Visual SourceSafe, and we had the following problem twice: We migrate files manually (get from VSS, add in TS), and with two files (in different projects), the content of the file was changed. The first file was an XML file which ended up with a C# class definition. In the other case, an include file was transformed into a Registry file (like the ones RegEdit create). The content of both files are the same as other, unrelated files within TeamSystem. To clarify: The file names were not changes, but the content, to something entirely different and unrelated.
Has anybody else experienced this? The first time we just thought of some sort of awkward human mistake, but not twice. Very strange, and very discomforting.
Best regards,
Martin
Martin,
Funny (not really) you received this today, because I spent the whole day trying to recover from the same problem. We did a restore last week and followed all the steps to get everything working. Today we decided to create new projects on a new template and move the source control from one project to the new project.
After the move and checkin of the source control we noticed very strange things happen. The source code on the developer machine was totally messed up. Some files were deleted with no way to trace back to them. So we tried to just get the latest source code from the new project. After opening it up, in the app.config file was the entire contents of another form. Also the assembly manifest file had source code from another form. To sum it up, after 8 hours working with the developer we were able to restore his machines backup and get the correct versions of the files to check it back in. I tried this with another project and found very similar results.
I have suggested to the developers in our company to not utilize the move feature but to unbind the projects from the old project and bind it to the new project. We will lose the history, but it may be worth it rather than running into errors like this.
If anyone happens to find the solution to this problem that would be awesome. For now, we are just going to do things the long way around.
BTW we had to run the http://team foundation server:8080/WorkItemTracking/v1.0/ClientService.asmx to stamp the work item cache so we could create new team projects. Is this the correct method to flush the app tier cache?
Aaron
Richard,
Indeed, we did a restore last week. We have now deleted the cache as you described and we're hoping never to see such problems again ;-)
If we do, you'll know :-)
Btw, the directory you stated does not seem to be correct, it's 'Data\<some GUID>'. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=251502&SiteID=1
Edit: Oh, that post was by you also...
Thanks,
Martin
