Our TFS server went down yesterday, so I had to work offline. After changing a large number of files, the administrators found that the DNS problem and the alias that we used for TFS did not work anymore, so we had to go to the IP address of the TFS server.
With this change, my solution could not be bound to the "new" TFS server. So I did this to remove the binding of my solution from the idle alias of the TFS server and associate it with the "new" server.
It seemed to work. I was really afraid of the number of manual mergers that I had to do after receiving the latter, but, to my surprise, they were not there.
I noticed the beginning of the weirdness when I continued to work on some modified files. Despite the fact that the files turned out to be fixed, there were actually a few seconds of lag before I could perform my first modification, which meant that the file was reinstalled. I did not pay attention to it, so I postponed my changes the next day.
The next day, we received the latest versions and found that some files that I changed from the previous day are marked. However, looking at the history and matching confirmed that I had not yet verified my new changes and that my local version was different from the latest version of TFS.
Now I have a bit of trouble remembering my modified files, but I could probably take a look at the last rack I made and work with this list. It’s just very disappointing that I will need to make an extract for each of these files before I can finally check them again.
Is there an easier way for TFS to recognize modified files? Also, the bulkhead was probably the reason why this happened if I did it differently?
Edit: I just looked at the details of my last shelf, and my modified files were not included. So much for that.
Edit 2: I accidentally opened my solution offline, and when I went online, he was able to detect files that were changed, fortunately. But the question still remains, what should I do differently so that this does not happen again?