Internal dogfooder reported this tip today: The recommended install sequence is VSTS and then installing the TF client. However if you accidentally install TF client first, and then VSTS, and you don't see the standard TFS menu choices when you open the...

(Update: Skip straight to a great answer to this question by Travis Owens ) I just got an email from a Microsoft customer (who will remain nameless) who is trying to improve their company's intranet. They wanted me to give them some insight into Microsoft...

This is pretty much a brain dump of things to be aware of when combining ASP.NET and Team Build - not for the faint of heart, we are talking beta/CTP here (and I don't have the luxury of being able to go back and try all of this on Beta 2), but it can...

Update: MSDN documentation here: http://msdn2.microsoft.com/library/ms181247(en-us,vs.80).aspx "Your mileage may vary" on this tip - in fact I can practically guarantee it won't work for you if you are still on Beta 2 like you probably are. But for...

Here are a few things about branching source code in VSTS via the IDE that I've learned the hard way: First, don't try to branch the top most level node of the Team Project. Branch subfolders . At least in the beta, the root itself of the Team Project...

I'm going to keep adding to this entry with any ideas/suggestions I have for troubleshooting various error messages, etc. It's barebones now but I hope to keep updating it. If you need help troubleshooting some VSTS problem that is not documented here...

http://teamsystemrocks.com/

This isn't a black belt rocket scientist VSTS tip by any means but it's an important one to master if you ever want to log a bug. To create a new work item (AKA "bug"), right click on the Work Items folder in the Team Explorer window and in the resultant...

Here's a site aggregating a lot of different software testing (er, SQA - Software Quality Assurance) information, didn't see anything on our VSTS testing tools there yet (give it time), but it's worth checking out: http://sqa.fyicenter.com

VSTS is sometimes like the Franklin Institute in Philadelphia was for me as a New Jersey school kid - despite your best efforts to prove the chaperones wrong, you really can't cram it all into your 8 year old head on one field trip. Anyway, drumroll please...

OK, so this is for all those people using beta builds out there. There is a client side cache involved with connecting to remote TFS application tier machines. Unfortunately it can be somewhat buggy in the beta builds, leaving you with an error message...

OK, this might be a stretch, but since VSTS has so many touchpoints with SQL Server 2005, I figured this couldn't hurt. Benjamin Jones pointed this out -- free online courses until November 1, 2006: http://www.microsoftelearning.com/sqlserver2005/

In VSTS work item tracking, there is a special identifier called @me instead of a specific user alias so that the user who is running the query sees only those bugs that have AssignedTo= their alias, for example. This is helpful if you want to create...

http://channel9.msdn.com/ShowPost.aspx?PostID=85529#85529

for those of you who dream in dhtml - http://weblogs.asp.net/scottgu/archive/2005/06/28/416185.aspx

If you're really curious about VSTS and blogs aren't giving you enough regular info, and you use an RSS aggregator for getting your information, consider subscribing to the following MSDN Forum RSS feeds: VSTS Software Testers: http://forums.microsoft...

Code analysis messages against ASP.NET projects have greatly improved in the private drops I'm testing. One of the things that caught me off guard in the earlier builds was that some warnings and error messages had no associated file names or line numbers...