If you have ever user Team System Web Access to work with TFS, specifically the Documents tab, you may have discovered that it is possible to open documents via this interface, but if you try to save your changes back to TFS you can’t do it… or at least not as easily as you could if you had opened the document via Team Explorer. Take the following scenario for example: let’s say there’s a team project with a SharePoint document library at http://sharepoint/site1/ and the user has Microsoft Word as the registered handler for .DOC files on their machine:
Using Team Explorer
Using Team System Web Access (TSWA)
The key thing to remember is that TSWA acts as a gateway between the user and the SharePoint. The reason that TSWA works this way is because there are certain scenarios where the end user might not have direct access to the SharePoint server (for example, I expose TSWA to the Internet, but my TFS, SharePoint and Reporting sites are not externally accessible from the Internet).
Currently, we’re using the same approach for TSWA 2010 (which is now a part of TFS 2010). However, TSWA 2010 will provide a way to directly access the documents on SharePoint:
I hope this help you understand the differences in document modification between TSWA and Team Explorer. Admittedly it is less convenient to modify documents via TSWA, but if you take a few moments to reference the “How to: Check Documents In and Out of a Document Library (Team System Web Access)” topic on MSDN you will see that it is just a few more clicks of the mouse, ultimately – both TSWA and Team Explorer can provide access to and versioning of your TFS documents.
PS: Thanks to Chris Cooper & Hakan Eskici for their contributions to this post.
Michael Ruminer on Here's The Deal When Your Code Compiles But At Runtime It Can't Find Some
I get the tech explaination but it's still an unintuative and lame requirement. Google the question and see how many different theories people have come up with to "fix" the problem - because they think it's some kind of bug or incompatibility. This needs work. I'd say either "fix" it or make the UI interaction a bit more informative so the user understands how to perform this basic task.