Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / C# / January 2008

Tip: Looking for answers? Try searching our database.

using class diagram in VS 2005

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Tony Johansson - 12 Jan 2008 15:59 GMT
Hello!

I try to use the class diagram feature in VS 2005 but the drawing is
different se below.

If I have an Interface that "implement" two other interface these vill be
shown with arrows pointing to the top interface which is correct.

If I instead have a class that implement an interface these will not be
shown with arrows in the class diagram. What is the reason for not using
arrows as in the example when having only interfaces.

I just wonder which is best to use explicit inherit implementation or
implicit implementation.

I suppose that you will say that sometimes is the explicit inherit
implementation best and sometimes is the implicit inherit implementation
best.

//Tony
Marc Gravell - 12 Jan 2008 20:31 GMT
> If I instead have a class that implement an interface these will not be
> shown with arrows in the class diagram.
Looks like fairly standard UML-representation to me... the arrow
implies inheritance, which isn't the case for an interface
implementation (the lollipop). I don't know what other tools would
offer, but I've never found this a problem.

> I just wonder which is best to use explicit inherit implementation or
> implicit implementation.

If it makes sense for a regular caller to use the methods, then make
it implicit (since you want the public methods anyway).
If the interface is only used in specific circumstances
(ICustomTypeDescriptor, ITypedList, for example) - then make it
explicit.
If the names would be confusing, or you implement 2 interfaces with
the same method name (but different meaning) then use explicit.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.