C# reverse engineering / diagramming

[jaschag]

Hi,

After reverse engineering an assembly, is it possible to stop the property getters/setters from showing in a diagram? When I uncheck the Property Methods checkbox, the properties disappear but the getters/setters are still shown - is this the correct behaviour?

Thanks,

Jascha

[Paolo F Cantoni]

Hi Jascha,

Can you post an exact illustration of what's happening before and after you set the check box.

I have some issues with the way EA handles Properties in general (See: [size=13]Property Redux[/size]).  But I'm not sure I've seen what you're describing.

It may be you haven't got the settings right, but until we see exactly what you mean, it's difficult to suggest a remedy as EA has a UI (Unique Interface)

Paolo

[jaschag]

Hi Paolo,

I wasn't sure how to add images easily so I will describe in a bit more detail. Assume a class:

public class MyClass
{
 public int MyProperty
 {
   get {...}
   set {...}
 }
}

With the following checked in diagram property settings:

Visible Compartiments: Operations
Visible Class Members: Public, Property Methods

I see

===
get_MyProperty
set_MyProperty
---
MyProperty
===

If I uncheck Property Methods, I only see

===
get_MyProperty
set_MyProperty
===

What I want to do is see the property but not the accessor methods but I can find no combination of settings that achieves this.

Thanks,

Jascha

[Paolo F Cantoni]

HI Jascha,
Check the language settings of BOTH the Class and the property dialog of the property itself.

IIRC, even if you set the language property to C#, the property doesn't default tot he language setting of the class.

Did you read my redux?  For C#, the getters and setters shouldn't be named in that way (IIRC if the settings are correct, they aren't).

Let me know what you find and what happens if you play with the settings.

Oh, what version of EA are you using?

Paolo

[jaschag]

Hi Paolo,

These classes are a result on a reverse engineer on a .net 2 assembly (originally C#) so I do not control the naming of the property accessor methods. You were right that the classes were not marked as C# but when I do mark them as such it makes no difference. There seems to be no way to specify the language of the class members themselves (as I would expect) so no go in that respect. I noticed that the properties are marked correctly with the property stereotype (but there is no specific property method stereotype). My feeling is that the visibility setting for Propery Methods should specify the visibility of the properyy accessors (getters/setters) and not the properties themselves but this is not what happens. I still cannot find a setting config that shows the properties but not the accessors so I have had to manually delete all the accessors which is a pain in the **** to say the least. I am an EA fan but the reverse engineering and this specific issue have dented my faith slightly. If you have any other suggestions I would be very happy to try them.

Thanks again,

Jascha

[Paolo F Cantoni]

You can change the language specifically for Property members.  I think you still need to check what language the Properties are being set to.  Check the little builder [...] button to the right of the Property name in the Attributes dialog.

Paolo

[jaschag]

Check the little builder [...] button to the right of the Property name in the Attributes dialog.

There is no builder button there and all the other ones do not allow language selection. Also, the properties have been imported as operations and not attributes which may or may not be correct (I would have expected attributes).

Jascha

[Eve]

You will see the behaviour described (properties, plus the separate accessor methods hidden normally by .Net) when importing .Net assemblies by disassembly.  You only get the property stereotyped methods when importing from .Net, and in version 7 we've also stripped out the special get_ and set_ methods for disassembly import.

[jaschag]

You will see the behaviour described (properties, plus the separate accessor methods hidden normally by .Net) when importing .Net assemblies by disassembly.  You only get the property stereotyped methods when importing from .Net, and in version 7 we've also stripped out the special get_ and set_ methods for disassembly import.

Ok, so I need version 7 - is there a release date?

May I ask why properties are imported as Operations as opposed to Attributes?

[mikewhit]

May I ask why properties are imported as Operations as opposed to Attributes?

1) STFF

2) http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=general;action=search

3)

• http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=UMLPRO;action=display;num=1151590177;
  

[jaschag]

3) Thank you very much

1) TOTM?