Using VS2008 Pro evaluation version we've had the delightful experience of losing about 12 man-hours of work today (first day with it) because apparently it has problems with VSS 2005 integration.

Having configured VS to automatically check out files when editing and to automatically check in when closing, we blissfully didn't think we had to test the functionality that has worked fine in VS2005 for years.

Wrong.

We realized things weren't being automatically checked out. That's bad enough. Then we set advanced options to not download VSS version of files when checking out (so we would not overwrite our changes before checking in). Guess what. We're back to the original version of our website because from what I can tell VS2008 didn't check in the files when we told it to.

There isn't a real fix, only a CTP of an update to VSS2005 that *apparently* will make up for the VS2008 problem.

See..
http://msmvps.com/blogs/theproblemsolver/default.aspx
and
http://www.microsoft.com/downloads/details.aspx?FamilyID=FAF41EDD-924D-449F-AEFC-9C86DD499720&displaylang=en

I also see that whatever VS2008 does may also screw up VS2005 if you have that installed. I gotta check my development machines at home.

Crap.

If the VSS2005 CTP update doesn't fix that, we're back to VS2005. Broken source control integration is a complete showstopper in my book, and it should have been for Microsoft.