Jeff Atwood at Verigo Software has posted a nice visual guide to backing up your TFS data (based on the official MSDN TFS backup documentation).
A Visual Guide to Backing Up a Team Foundation Server database
He promises to provide a guide to restoring the data as well.
There's a helpful FAQ posted in the ASP.NET forums regarding using Team Foundation Server with the newly released Web Application Projects for Visual Studio.
Issue 6 - Using TFS Team Build
Issue 6 - Using TFS Team BuildThe May 2006 release of Web Application Projects supports building with Team Build on a Team Foundation Server (TFS). However, you will need to manually add the "Microsoft.WebApplication.targets" file to your Team Foundation Server for it to work. On the computer running Team Build, navigate to the "C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0" directory. In this directory create a "WebApplications" directory. Place the "Microsoft.WebApplication.targets" file in the "WebApplications" directory. This file can be found at the same location on your developer system that has been updated with the May 2006 release of Web Application Projects. After performing these steps Team Build should be able to successfully build a web-project build with the new Web Application Project type. Additionally, if you have an older version of a Web Application Project, you will need to add the WebApplication.targets line (shown in blue and bold) after the normal CSharp.targets or VBasic.targets line in your .csproj or .vbproj file (all new or newly migrated projects will have this line automatically). <Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" /><Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v8.0\WebApplications\Microsoft.WebApplication.targets" />
Issue 6 - Using TFS Team BuildThe May 2006 release of Web Application Projects supports building with Team Build on a Team Foundation Server (TFS). However, you will need to manually add the "Microsoft.WebApplication.targets" file to your Team Foundation Server for it to work.
After performing these steps Team Build should be able to successfully build a web-project build with the new Web Application Project type.
Additionally, if you have an older version of a Web Application Project, you will need to add the WebApplication.targets line (shown in blue and bold) after the normal CSharp.targets or VBasic.targets line in your .csproj or .vbproj file (all new or newly migrated projects will have this line automatically).
<Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" /><Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v8.0\WebApplications\Microsoft.WebApplication.targets" />
Issue 7 - Using TFS Source Control
Issue 7 - Using TFS Source ControlThere is a known issue with the enterprise source control system in the Team Foundation Server (TFS) which incorrectly identifies codebehind classes for .aspx. and .ascx files as folders. To workaround, do not use "File/Source Control/Open from Source Control". Instead, manually get the solution using Team Explorer and open the solution from local disk. This problem will be fixed in a future release of Team Foundation Server.
Issue 7 - Using TFS Source ControlThere is a known issue with the enterprise source control system in the Team Foundation Server (TFS) which incorrectly identifies codebehind classes for .aspx. and .ascx files as folders.
To workaround, do not use "File/Source Control/Open from Source Control". Instead, manually get the solution using Team Explorer and open the solution from local disk.
This problem will be fixed in a future release of Team Foundation Server.
About a month ago, I wrote about using Outlook with RPC over HTTP. I recently stumbled across an old blog post by Jeremy Kelly called Using your Mailbox to Store Work-in-Progress documents. He mentions a feature called "free docs." Combining this with Outlook over HTTP is really very useful. Here's how it works.
What's so cool about that? It's a secure way to be able to work on your documents wherever you have Outlook over HTTP (office desktop, laptop elsewhere), the file is updated in place, automatically synchronized (no more searching for the latest version), and backed up for free on the Exchange server. By secure I mean that the documents are stored on the corporate exchange server, the communications with the Exchange server over the Internet are encrypted, and the documents only exist on machines under my control.
That's a lot more convenient than a thumb drive or emailing document attachments to yourself.
The part I'd like to be able to do is to combine steps 1 and 2 by being able to directly create the document in the Outlook folder without having to go through the intermediate step of creating a file to be dragged into Outlook. If anyone out there knows how to do that, please let me know.
I wrote this snippet recently to compare the edited files in a shelveset with an arbitrary checked-in version of the same files. It's another example of how to use the API to show differences. See How to compare (diff) trees at different versions using the API for a different example of comparing checked-in files.
If you are just getting started with the version control API, you'll want to start with the basic example.