Book a Demo

Author Topic: Issues Importing C# Source (Generalization Links)  (Read 2516 times)

Phil_Prasek

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Issues Importing C# Source (Generalization Links)
« on: October 05, 2003, 07:12:46 pm »
In general I am very impressed with the job EA does importing from sources, however I am encoutering issues in a couple places.  Both of these issues relate to generalization relationship links not being created when C# source is imported (via import source directory).

I'm importing approx. 100+ packages into the model and without these generalization links being created I'm experiencing two main problems:
1) The relationship matrix wont have the info it needs to show the relationships.
2) The inherited methods for collaboration/sequence diagrams are not available in the methods drop down.

I can manually add the generalization link when doing the sequence/collaboration diagrams (since I know what classes I'm dealing with).  However with the relationship matrix this is more of an issue since I was hoping to use that to map out the dependencies of some packages we were thinking of moving around.

I haven't had a chance to create an isolated repro case but I thought I'd run it by you guys in case they're already known issues.

Thanks,
Phil

========================================
Case #1
Importing a file that contains a class that inherits from a base class in a different namespace (base class located in seperate file).  

Note the use of [System.Serializable()] here instead of [Serializable].  This was one thing that stood out as being different.

-------------
namespace Test.P1.P2.P3
{
   
   
   /// <summary>
   ///     omitted
   /// </summary>
   [System.Serializable()]
   public class MyClass : Test.P4.P5.MyBaseClass
   {
      ...
   }

Expected Behavior:
Generalization link is created

Actual Behavior:
No generalization link is created, but the name of the base class still appears in the upper right corner of the class in the diagram.

========================================
Case #2
Importing a file that contains a class that inherits from a base class in a different namespace (base class located in the *same* file as the subclass).  

---------------------
using System;
using System.Reflection;
using System.Collections;

namespace Test.P8.P9
{
   /// <summary>Autogenerated on 11:38:31 AM</summary>
   public abstract class MyBaseClass
   {
        ...
   }  
}
namespace Test.P6.P7
{
   /// <summary>Autogenerated on 11:38:31 AM</summary>
   public abstract class MyClass : Test.P8.P9.MyBaseClass
   {
        ...
   }  
}

Expected Behavior:
Generalization link is created

Actual Behavior:
No generalization link is created, but the name of the base class still appears in the upper right corner of the class in the diagram.
« Last Edit: October 05, 2003, 07:42:02 pm by Phil_Prasek »