1
Suggestions and Requests / Re: Support for newer programming constructs in C#
« on: November 13, 2009, 04:45:17 pm »
Example 1:
There is an Employee class with a many-to-many relationship to the Territory class. This relationship shows up in the class diagram as follows:
In the Employee class (use of generics):
territories: IList<Territory> new List<Territory>
In the Territory class (use of generics and Automatic Properties):
Employees() IList<Employee>
Reverse engineering this relationship to a class diagram doesn't produce any connectors between these two classes. Visually, there is no obvious indication that there is a relationship.
This would be really cool.
AFAIK currently only umodel has this => please add this that we are also able to work with current C# language constructs in EA. 8-)
There is an Employee class with a many-to-many relationship to the Territory class. This relationship shows up in the class diagram as follows:
In the Employee class (use of generics):
territories: IList<Territory> new List<Territory>
In the Territory class (use of generics and Automatic Properties):
Employees() IList<Employee>
Reverse engineering this relationship to a class diagram doesn't produce any connectors between these two classes. Visually, there is no obvious indication that there is a relationship.
This would be really cool.
AFAIK currently only umodel has this => please add this that we are also able to work with current C# language constructs in EA. 8-)