Hello,
I am looking into various ways to increase communication across our many
developers: XML commenting, generating CHM files using Sandcastle, Visio UML
diagrams, etc.
My question is, how does the Class Diagram within Visual Studio add value?
It seems that while coding, it doesn't offer anything that is not in the
Object Browser. And with regard to documentation, it isn't robust enough
(compared to Visio) to use.
Has anyone had successes/failures using VS Class Diagrams? Any insight
would be appreciated.
Thanks,
newGuy
Scott M. - 04 Sep 2007 23:53 GMT
Well, first and foremost, a picture is worth a thousand words (as they say).
The Object Browser doesn't give you this pictoral sense of your classes nor
does it show anything but a single class's linear inheritance chain, while
the Class Diagram can show multiple relationships.
In addition, the Class Diagram is a gateway to the Class Designer, which can
increase productivity treamendously.
> Hello,
>
[quoted text clipped - 14 lines]
>
> newGuy
newGuy - 05 Sep 2007 14:52 GMT
Ah! Didn't even think about the Class Designer. Thank you for the response,
Scott.
newGuy
> Well, first and foremost, a picture is worth a thousand words (as they say).
> The Object Browser doesn't give you this pictoral sense of your classes nor
[quoted text clipped - 22 lines]
> >
> > newGuy