Why I don’t recommend my customers to rely on Visual studio for development.
Abstract
The only way to edit architecture and modelling with Visual studio is to buy the very expensive Ultimate edition. This means that it will be not everyone can be involved in the process of evolving the solution.
TL;DR
Development requires Architecting an Architecture in some way or another. This architecture is not written in stone but changes as time or business changes; we call it requirements change.
In the old days, like 20 years ago, I learned that there is an architecture phase and then a development phase. This is not considered best practice any more. Also not best practice is to have silos with Architectures and Testers and Coders and Database managers.
This is where Microsoft and Visual studio fails. Not technically but license wise.
Look at this part of a comparison chart for different Visual studio versions. It clearly explains that Architects must have the Ultimate edition and that no one but Architects are allowed to change any Architect document. (the Ultimate edition is way more expensive than the others)
Visual studio comparison fail where it shows that only Ultimate can edit architecture stuff. Original from Wikipedia.
Tags: architecture, fail, visual studio