>Jeroen,
>
>Visual Studio *may* be all about that someday, but it is nowhere near so today! For all intents and purposes, for instance, VFP is an orphan there at this time (with promise for better later - it can't happen overnight they tell me).
>
>What's wrong with Visual Studio being used by multiple in any organization? - I've got to believe that THAT was MS' real intent with the product, at the very least for the time being (several persons, each learning/using one or two different of the components to deliver an "enterprise" solution.

Actually, if you're leading a project which involves more than one tool, you should be a master in project-running, and know your main language to the last neck of its woods. Then, you should know the other languages to the extent of knowing what are they good for, what are their drawbacks - and know the person to entrast that part of the project to. And you're using VS - as a team tool, not as a Swiss army knife for a single programer. This layout makes much more sense to me.