Book a Demo

Author Topic: Import c#, and Inherited methods  (Read 3034 times)

petermodonnell

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Import c#, and Inherited methods
« on: April 28, 2005, 05:13:32 am »
Im new to EA. I've imported some CS files, and have made a sequence diagram, I'd like to model behaviour involving inherited methods e.g for a TextBox.
I've ticked "Inherited Features..Show operations",
but none of the methods appear, when I try to model a call.

Do I need to imprt the System.Web.UI.WebControls or something,
regards

Peter

thomaskilian

  • Guest
Re: Import c#, and Inherited methods
« Reply #1 on: April 28, 2005, 07:57:22 am »
Make sure the import really has created an inheritance. Select the generalized class and open the relations window. You should see a generalization relation. If not, create it manually. You should then see the operations of the parent class.

petermodonnell

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Import c#, and Inherited methods
« Reply #2 on: April 28, 2005, 10:34:10 am »
No luck.
I'm using the trial version. In the class diagram, those classes that generalize System.web.ui... have "System.web.ui..." in the top right hand of the box.
The Relationship window shows their child relationhips, but not the parent relationships (to System.web etc).




thomaskilian

  • Guest
Re: Import c#, and Inherited methods
« Reply #3 on: April 28, 2005, 12:31:11 pm »
As long as you don't have the parent classes you won't have access to their methods. Maybe you can get those via XMI from somewhere else or someone in this community has an answer. Sorry

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Import c#, and Inherited methods
« Reply #4 on: April 28, 2005, 04:15:03 pm »
As Thomas says, if you don't have the parent classes in your model (and you won't unless you have explicitly imported them)  The header that EA is showing you is that it knows the class has a relationship to a class (or interface) "System.web.ui"

You can confirm that there is no actual relationship by selecting your class and selecting Element | Set Parents and Interfaces.  Each parent will be shown there.  If there is actually a link it would have a yes in the owned column.

In 5.0 you will be able to import from .net assemblies and get these classes into you model.  Until then, there has been some discussion on this forum about importing .net libraries.  You may be able to apply some of the ideas discussed there.

Simon