Newbis
asked on
How to start over with Team Foundation Server
I have a Visual Studio 2012 solution that was connected to Team Foundation Server. Unfortunately, I deleted some files in my project, and added them back. (I didn't realize that once a file is deleted in VS, a file with the same name and location can never be added back to TFS.) After trying to rollback and then redo changes several times, it got to where there were many conflicts that couldn't be resolved. Plus the mere process of checking things in tended to change my project so it wouldn't run. (Fortunately, I made a few different backups of the project on my local drive, as I realized that at this point TFS had gotten very messed up.)
So what I'm trying to do now is to start over...to basically create a whole new repository on TFS for the project and start from scratch. But it's not cooperating. Here's what I tried: I went to File | Source Control | Advanced | Changed Source Control, and then selected "Unbind" for my solution and its projects. Then I tried to re-add the project to Source Control, creating a new folder. It complained that the project is already in source control. However, I went out of VS and came back, and went back to "Change Source Control," and selected "Bind," and the Server Bindings gave a path that matched my new folder name that I had just created. So I thought that this was okay, and I tried to check everything in. But it only wanted to check in the few files that were different from the old repository (the one that I'm trying to get away from). And sure enough, even if I tried to check those few files in, it says there are all sorts of conflicts. So even though the "Server Binding" for the Solution and Projects points to a newly created folder, it still remembers where it was pointing before.
So I repeated the above steps, except that this time, I deleted the .suo file and also the source control meta data files for my solution and project. I also looked in the solution and project files themselves to see if there were any references to Team Foundation Server, but I did not find any. However, when I tried to bind to a new folder name in the TFS server, it still acted as if it was connected to the original messed-up repository.
Is there a way to make it forget about the old repository and just start from scratch?
So what I'm trying to do now is to start over...to basically create a whole new repository on TFS for the project and start from scratch. But it's not cooperating. Here's what I tried: I went to File | Source Control | Advanced | Changed Source Control, and then selected "Unbind" for my solution and its projects. Then I tried to re-add the project to Source Control, creating a new folder. It complained that the project is already in source control. However, I went out of VS and came back, and went back to "Change Source Control," and selected "Bind," and the Server Bindings gave a path that matched my new folder name that I had just created. So I thought that this was okay, and I tried to check everything in. But it only wanted to check in the few files that were different from the old repository (the one that I'm trying to get away from). And sure enough, even if I tried to check those few files in, it says there are all sorts of conflicts. So even though the "Server Binding" for the Solution and Projects points to a newly created folder, it still remembers where it was pointing before.
So I repeated the above steps, except that this time, I deleted the .suo file and also the source control meta data files for my solution and project. I also looked in the solution and project files themselves to see if there were any references to Team Foundation Server, but I did not find any. However, when I tried to bind to a new folder name in the TFS server, it still acted as if it was connected to the original messed-up repository.
Is there a way to make it forget about the old repository and just start from scratch?
ASKER
I thought I had deleted the XML stuff, but I must not have, because when tried it again after posting this, I did find that there was TF stuff in the file after all, and it deleted it, and then it worked.
Odd thing was that once all that was deleted, I could no longer pick the name of the new folder. Fortunately, it remembered the name of the new folder that I was attempting to create before, so it used that.
Odd thing was that once all that was deleted, I could no longer pick the name of the new folder. Fortunately, it remembered the name of the new folder that I was attempting to create before, so it used that.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I am not sure what that means.
<SccProjectName>SAK</SccPr
<SccLocalPath>SAK</SccLoca
<SccAuxPath>SAK</SccAuxPat
<SccProvider>SAK</SccProvi