A picture is worth a thousand words

Speaking of the Class Designer

Harry Pierson's DevHawk Weblog — Sat, 26 Feb 2005 07:35:00 GMT

re: A picture is worth a thousand words

Bil Simser — Sun, 27 Feb 2005 09:10:00 GMT

Nice stuff. I'm really looking forward to the release and have been working with the alphas/betas since mid last year. This stuff just plain rocks and Software Factories are going to just plain shift mindsets.

One question is that I would like to switch documenting my systems that I'm currently building in Visio. Our standard is to use UML and the Visio templates are not bad but I would like to use the look and feel that the VSTS designers use, even if they aren't functional like they are in Class Designer.

Any chance of getting some Visio templates so that when we are ready to move to the new system, we could import our old diagrams to create working systems (as much as they can). Sort of how you can import Visio diagrams into BizTalk 2004?

re: A picture is worth a thousand words

Sun, 27 Feb 2005 11:15:00 GMT

Can it export to the standard UML XML format for importing into other UML designer tools?

And lo! by imariano

Architecture — Mon, 28 Feb 2005 16:31:00 GMT

If you haven't already, take a [http://blogs.msdn.com/classdesigner/archive/2005/02/25/380023.aspx|look at the next generation Class Designer] that the Visual Studio team have been working on. It's q

re: A picture is worth a thousand words

patrick — Wed, 02 Mar 2005 12:00:00 GMT

Wrt exporting to the UML XML format, I am assuming you're referring to the XMI export. No, it will not be in this V1 release. Since you broght it up, I wonder what's you thoughts on mapping custom attribute (in C#) to the UML construct (custom defined stereotype?). I've been working in the UML tools (ie Visio software modeling) in the past and often found that there's a gap between the UML and the actual programming language. When we initially design our meta-model (for capturing the language), we've struggled a little bit and finally decided to model accordingly to the language (as opposed to modeling it closely to the UML meta-model). By following this approach, it allows us to model the user's code straightforwardly...

New Team System Stuff - 2005-03-02

Rob Caron's Blog — Wed, 02 Mar 2005 21:56:00 GMT

re: A picture is worth a thousand words

Marlon Smith — Wed, 09 Mar 2005 09:25:00 GMT

Does the Class Designer have support for Attributes?

re: A picture is worth a thousand words

Patrick — Thu, 10 Mar 2005 13:31:00 GMT

In CD, we did not make any special treatment for Attribute. It would just be a regular class whose parent happens to be System.Attribute (or its descendents). You can right-click the shape to "ShowBaseClass" of the attribute class and you shall see System.Attribute as its parent (or its descendent). You can create a new attribue class by using the inheritance line tool between your class and the System.Attribute (or any existing attribute class in the diagram.).
You can also consume the attribute by using the Attribute dialog box. You can launch this dialog box by 1.) Selecting the class shape. 2.) Go to the property window, click the "..." tunnel button in the "Custom Attribute" row within the grid. This allows you to specify attributes associated to the class.

re: Modeling as a Productivity Enhancer in Visual Studio Team System

Barry Gervin's Software Architecture Perspectives — Sun, 20 Mar 2005 07:12:00 GMT

Interview with John Stallo

ClassDesigner's WebLog — Wed, 30 Mar 2005 20:30:00 GMT

John Stallo - The Visual Studio 2005 Class Designer (1 of 3)

TrackBack — Thu, 21 Jun 2007 15:15:22 GMT

I've now done a few interviews with my co-workers building Visual Studio 2005.

ClassDesigner s WebLog A picture is worth a thousand words | Insomnia Cure

ClassDesigner s WebLog A picture is worth a thousand words | Insomnia Cure — Wed, 10 Jun 2009 03:35:41 GMT

PingBack from http://insomniacuresite.info/story.php?id=4167