I went yesterday to the Microsoft Visual Studio 2005 launch event.
In the new Visual Studio, Microsoft integrated a source control system,
team collaboration (tasks and bug tracking), load testing and functional
There are 2 problems with this approach IMHO:
1. This goes against best-of-breeds environments, where people want to
use the best source control system, best IDE, best bug and task tracking
systems, etc. For example, I would prefer having good integration of my
IDE with the source control system I choose to use.
2. Multi-disciplinary environments suffer. For example, in a combined
C++ and Java environment one can't use the source control system and bug
tracking in Visual Studio 2005 as it is a one-off solution rather than
integration with a source control system from both the C++ and Java IDEs.
With that in mind I have to question the Demetra quest to have source
control and other components of the software development life cycle
embedded. I doubt it will be of use to our heterogeneous environment,
and I have to question whether a version 1 component (in IDEA or Visual
Studio) will be better and more reliable than existing tools
(Subversion, StarTeam, Perforce, etc.) or if a task and bug tracking
system will be better than existing products (e.g. Rally).
What I really want to know is if the source control API will stop being
developed, if I should expect the Subversion or Perforce integration
become stale and if I shouldn't hope for integrating with any bug
tracking or task tracking system as a result of this new do-all-be-all