I had all kinds of fun getting this to work - so I'm going to record it in case I have to do it again.

1: Make sure TFS2008 Explorer is Installed
2: Install VS2008 SP1 (this Updates VS2008 & TFS2008 Explorer)
3: Install TFS2010 Forward Compatibility Fix (must have SP1 installed or it will refuse to do anything)

When you connect to the server, you will have to use the full URL to VS2010, for example:

http://teamServer:8080/tfs/<collectionname>

If SP1 and the Forward compatibility tool aren't installed, you'll get an error about the server name cannot contain "://" or similar.  Make sure you don't have a trailing '/' either.

Useful Links:

Most of this is better explained in Jason Barile's blog post (which, of course, I didn’t find until I almost had it working but this got me over the URL hump):
http://blogs.msdn.com/b/jasonba/archive/2009/08/10/how-to-connect-to-a-tfs-2010-server-from-a-2008-team-explorer-client.aspx

Visual Studio Team System 2008 Service Pack 1 Forward Compatibility Update for Team Foundation Server 2010 (Installer)
http://www.microsoft.com/downloads/details.aspx?FamilyID=CF13EA45-D17B-4EDC-8E6C-6C5B208EC54D&displaylang=en

Yet another Note to Self post--

In almost all the cases where I’m working on projects, I have multiple assemblies in the solution… In a lot of cases, I’ll make changes in one of the dependencies of my solution and when I get to a later step in the build, something else breaks.

A lot of the time, once I work my way back through the pack of build errors, I’ll find that way up my dependency tree, one of my projects had a compile error and it has trickled down through the rest of the build, causing one error after another.

A long time ago, from a source unknown to me now  I found a snippet of a Visual Studio Macro that got close to what I wanted and over the years, I’ve done some slight modifications and improvements to it and still use it.  It’s really simple, but it something that helps my workflow in small but measureable way.

So here is what I do… [after the break]

I was asked to setup one of our Web Servers to only Restrict all but a certain subset of IP addresses to have access to the site since this is a server that sits in our DMZ, I have basically two sets of addresses to allow in; our internal subnet of addresses and the clients’ external IP address.

I always keep looking for this information because for some reason it never sticks in my memory.  So I figured I’d put it some place I could find it without having to search for it every time…

This is a great resource for basically figuring out every kind of path or URI reference you can with ASP.NET:

From Rick Strahl’s blog:  http://www.west-wind.com/weblog/posts/132081.aspx

I’m already busy enough at work – but there is always something to learn… always.  I have a really long list of stuff that I want to learn – but I don’t get to chip away at it like I used to – because of learning stuff for work…

So, this week, I’ve added a few new bits to my bucket (in terms of trial by fire) so lets see: