I just ran across the FTPOnline article Reporting on Vista Security and the VS Road Map and the following quote by Prashant Sridharan, Senior Product Manager for Visual Studio is very misleading:
Rosario, with the first community beta due at the end of 2007, is a Visual Studio Team System (VSTS) update, with new organization collaboration features. Sridharan pointed out that Microsoft's research showed that 60-70 percent of all Visual Studio users are also VSTS users, so regular updates and enhancements to that product are an important part of the Microsoft developer strategy.
Now, 60-70 percent of all Visual Studio users may have a flavor of VSTS installed on their machine (Team Suite or one of the Team Editions), but from what I've seen in the field, almost none of the developers are actually using any of the tools installed as part of VSTS. I have yet to run into someone actually using any of the following: Unit Testing, Code Coverage, Dynamic Code Analyzer, Static Code Analyzer, Code Profiler, no less any of the architecture tools: Application Designer, Logical Infrastructure Designer, or Deployment Designer. 60-70 percent of Visual Studio users have VSTS installed because it is part of their MSDN subscription, not because they are using it. And don't get me started about the confusion between the differences in the terms VSTS and Team Foundation System. Team Foundation System is one of the Visual Studio Team System products, but that doesn't mean that 60-70% of Visual Studio developers are using Team Foundation System, which, at first glance, is what I thought the quote was implying. TFS may be the hot thing in some enterprise development shops, but not in the RAD shops that are the core of VS users. Don't get me wrong, some of the tools in VSTS are good (and better than nothing), and more developers should be using either them or a similar product, but most of the developers I'm see out in the field are just now waking up to things like unit testing and code coverage. Yes, more developers should be using these tools, and better versions of the tools will help adoption, but don't try to claim that a majority of Visual Studio users are actually using them. It just isn't the case out in the "real" world.