Messages

1

General Board / Re: C# reverse engineering / diagramming

« on: April 18, 2007, 09:18:13 am »

3) Thank you very much

1) TOTM?

2

General Board / Re: C# reverse engineering / diagramming

« on: April 18, 2007, 06:13:44 am »

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?

3

General Board / Re: C# reverse engineering / diagramming

« on: April 15, 2007, 08:45:57 am »

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

4

General Board / Re: C# reverse engineering / diagramming

« on: April 15, 2007, 01:48:45 am »

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

5

General Board / Re: C# reverse engineering / diagramming

« on: April 14, 2007, 11:14:37 am »

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

6

General Board / C# reverse engineering / diagramming

« on: April 14, 2007, 02:31:04 am »

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

7

Uml Process / Re: Newbie question

« on: October 24, 2006, 01:25:52 pm »

Hi Paolo,

What a helpful forum

The appearance in the project browser is the same even when I have set both a run state and object state - only the element name is showing. The diagram shows the object state but not the run state. The [Set feature visibility]/[Hide object runstate...] is not checked...

I am using pro version 6.5.797.

Any ideas?

Jascha

8

Uml Process / Re: Newbie question

« on: October 24, 2006, 12:26:56 pm »

Yes I can do that but ea creates a new entry in the project database for the instance (i.e. in the browser) so I end up with multiple identical looking entries (all looking like the original class) in the browser that are annoying to say the least. What is the purpose of being forced to have all these dupicates in the browser? They seem to make it hard to work with and mess with documentation

9

Uml Process / Re: Newbie question

« on: October 24, 2006, 10:44:13 am »

Hi David,

Thanks for the quick reply. I have a statechart that models the states (in this example Unpaid, Paid). The activity in this case will most likely result in more than just a state change (i.e. an automated payment and associated payment record may be generated) so I would like to convey that in addition to the possible states (that a plain statechart would). I am using object flows as you suggest but I guess my issue is that I cannot drop the same object instance with the two different states on the diagram as input and output of the activity. Is there another way of doing this (I do not want to create a new object for each state it happens to appear on a diagram in)?

TIA,

Jascha

10

Uml Process / How to model process/activity input/output

« on: October 24, 2006, 08:29:57 am »

How should I model a process / activity that takes as "input" an object instance in a particular state and "outputs" the same instance in another state? E.g.

Order [unpaid] -> Process Payment -> Order [paid]

Thanks