I’m just about done reading Professional Team Foundation Serverand at the end I found this little gem:
This tip needs the Team Foundation Power Tool (tfpt.exe) to work.
When you are working offline you just clear the read-only attribute on the files you want to edit. Later, when you are online, you open the command line, navigate to your workspace and run:
Now the power tool will find all those writable files and create a change set from them.
If you do a
tf.exe get filename.ext
and get All files are up to date. back, it might be because your current directory is not correctly mapped to a folder in the Team Foundation Server project your root folder is mapped to.
It your server ‘tree’ looks like this:
ProjectName Source ClientCode ... ServerCode ... …and your local folders look like this: ProjectName Source ClientCode ... ServerCode .
Howard van Rooijen has created a template for creating listeners to Team Foundation Server events. This might come in handy since I was thinking of creating a TFS Listener for logview4net.
I am about to separate the SQL and EventLog listeners to an assembly for MS listeners. A TFS Listener is exactly what that would need.
Add: Share and store documents… Free.
According to this article from the dev team deleted files are not left in a label. This might lead to some nasty surprises when you are in to restructuring your code base (as we are now). It is nice that we can get files from a specific point in time instead.
Since I didn’t find this info the first time I searched I’ll add it here to.
This is what you have to do to get the Team Explorer to work correctly if your TFS Server has a different DNS name than it’s machine name.
…and what is really missing in that instruction is to disconnect/reconnect you project in Team Explorer since all URL’s are cached on the client.