Learn to use Visual Studio, Visual Studio Online, Application Insights and Team Foundation Server to decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle
In the first in a series of blog posts, I begin to look at the various community initiatives for Visual Studio Team System, the metrics that give an understanding of "community health", and our plans for the next year in these areas.
To read more, see http://blogs.msdn.com/vstsue/pages/community-health-for-visual-studio-team-system-part-1-details.aspx.
Content Lead, Team Edition for Database Professionals and member of the Visual Studio Team System Community Council
PingBack from http://blogs.msdn.com/vstsue/archive/2007/09/06/community-health-for-visual-studio-team-system-part-1.aspx
Considering all the links lead to this same page. I'd say our health isn't that great.
I believe that link just links back here... aka: self refering link... ;)
Okay, for the folks that reported my circular link, thanks. Apparently it's a bad idea to name your blog post and the linked article with the same name (despite the fact that MSDN tracks them separately, they both seem to have the same URL which makes it impossible for you folks to see the underlying article).
Michael Ruminer on Team System 2008 Virtual Machine Naming Issue. Trent Nix on Its about time I Got the...