Messages

1

Bugs and Issues / Re: Support of C# 3.x automatic properties

« on: March 24, 2016, 06:43:29 am »

I know it's a very old post but since Sparx didn't answer our very valuable question here is a workaround for reverse engineering and see the C# auto-implemented properties showing as class associations.

First of all this method is intend to help on just reverse engineering to facilitate the comprehension of large models AND NOT for bidirectional code engineering.

The key for the problem is the absence of an auto generated backing field for the C# compiler to represent the true UML association that cannot be represented based on methods. Just UML attributes.

Then isted of making reverse engineering based on source code files (.cs or what ever) make reverse engineering base on .Net binaries with Disassembly method (You be prompted to show the path to Peverify.exe, found on Microsoft SDKs). This way the assembly WILL contain the auto generated backing fields necessary to show the correct UML association.

Disadvantages:
You cannot show source code on any element as all will be fixed to file.dll/exe used on reverse engineer;
You cannot edit this reverse engineered elements to synchronize with original code if you have it;
You will see all anonymous types your code have;

But anyway it is still useful.

Hope it can help some of you!

Márcio Mônego

2

General Board / Re: Reverse Engineering of C# Auto-Properties

« on: March 24, 2016, 06:39:46 am »

I know it's a very old post but since Sparx didn't answer our very valuable question here is a workaround for reverse engineering and see the C# auto-implemented properties showing as class associations.

First of all this method is intend to help on just reverse engineering to facilitate the comprehension of large models AND NOT for bidirectional code engineering.

The key for the problem is the absence of an auto generated backing field for the C# compiler to represent the true UML association that cannot be represented based on methods as already stated by Jeff.

Then isted of making reverse engineering based on source code files (.cs or what ever) make reverse engineering base on .Net binaries with Disassembly method (You be prompted to show the path to Peverify.exe, found on Microsoft SDKs). This way the assembly WILL contain the auto generated backing fields necessary to show the correct UML association.

Disadvantages:
You cannot show source code on any element as all will be fixed to file.dll/exe used on reverse engineer;
You cannot edit this reverse engineered elements to synchronize with original code if you have it;
You will see all anonymous types your code have;

But anyway it is still useful.

Hope it can help some of you!

Márcio Mônego

3

Suggestions and Requests / Re: Set label visibility for whole diagram

« on: April 02, 2015, 12:34:58 pm »

It is boring on database specific diagrams witch were reverse engineered and there is for each table relation:
Source and Target roles: Pk_****, FK
Relationship condition: A_FK = B_PK
Multiplicity..
and so on

We want only multiplicity, and some variations without Source and Target without any value on diagram..

Maybe clicking on a label type (like PK_...) and context menu hide xxx type connector label...

Or a dialog for entire diagram like the Label Visibility with connector type filter, order, etc..

4

Suggestions and Requests / Re: Typescript Code Modeling Support

« on: April 02, 2015, 12:14:49 pm »

+1 vote
We are migrating a large extjs javascript codabase and it will be GREAT to document, inspect our front-end code on EA

5

Suggestions and Requests / Re: Glossary: ability to add links to sources

« on: August 14, 2014, 11:21:24 pm »

It will be great and useful to solve pluralization problems when a plural form of one item in Glossary is needed.

I use to create a second Glossary item in plural form to see context in Use Cases and all along.

For stability I don't duplicate the contents of the second item, then I just Wrote something like  See "Singular form", but EA doesn't show the "Singular form" as a link to "Singular form" glossary item and the reader needs to open glossary manually to see the content...

Márcio Mônego

6

Bugs and Issues / Re: Connectors behaving weird in v12

« on: April 02, 2015, 12:07:59 pm »

I noticed that changing zoom level objects are changing size and some times its position.

If you change the fit behavior to wrap then changing zoom will change that objects..

7

Bugs and Issues / Re: DisplayToc

« on: October 09, 2014, 04:35:58 am »

Hi all,

It was reported some times as bug. But we saw in some place on EA site that to avoid this you should publish the generated html to a web server like IIS.

On the image you posted I see the file:// protocol indicating that it was accessed locally.

Hope this can help you.

8

Bugs and Issues / EA Lite and navigation links that doesn't works

« on: July 31, 2014, 05:52:53 am »

Hi all,

I've noticed that links in use cases with structured scenarios may not be navigated using EA Lite edition.

We have small teams of Architects, Analysts and developers and we have fighting a long since old versions trying to use EA Lite to devs read the specifications without a fee of an full license.

Old versions most time had small bugs on generating html reports or rtf reports. Always some thing works on one scenario and not in other.

Many times using Word substitution doesn't works for some tokens, labels, titles on documentations templates;
Some project types translations were fixed on documentation generation.

We see the effort you have made to change this part of tool to work better and hope to see it working better soon.

We use a mix of SQL Server repository and TFS versioning schema to maintain and protect model.

Using EA lite the user can't navigate using the links of use case specification, either for glossary items, Context References and other links. We use a lot of links to Business Rules, modeled Messages, glossary items and so on.

Same happening on version-controlled packages in EA Full 11 to packages that I does not have checkout. It is an annoying thing. Some packages take minutes to checkout.

Generating HTML reports EA eats many line breaks and joins things in a ugly way.

We are trying version 11 with same bugs (1107).

I use this great tool since Version 6.5.

If I forgot something let me know.

Regards,
Márcio


UPDATE1: I saw that in some cases inside the same use case scenario step the same item with link was opening and other not...(different columns)

Trying a bit I realized that it was because in general we use other columns like "Uses" and "Results" to store some large text with things like interface neutral rules and other OBS. If we decrease the other columns size and increase a bit the column that owns the link the 3 button pop-up shows....

UPDATE 2: Links to included use cases still doesn't show in uses and results columns. In the Action column shows nice.

9

Bugs and Issues / EA Lite and navigation links that doesn't works

« on: July 31, 2014, 04:01:53 am »

Hi all,

I've noticed that links in use cases with structured scenarios may not be navigated using EA Lite edition.

We have small teams of Architects, Analysts and developers and we have fighting a long since old versions trying to use EA Lite to devs read the specifications without a fee of an full license.

Old versions most time had small bugs on generating html reports or rtf reports. Always some thing works on one scenario and not in other.

Many times using Word substitution doesn't works for some tokens, labels, titles on documentations templates;
Some project types translations were fixed on documentation generation.

We see the effort you have made to change this part of tool to work better and hope to see it working better soon.

We use a mix of SQL Server repository and TFS versioning schema to maintain and protect model.

Using EA lite the user can't navigate using the links of use case specification, either for glossary items, Context References and other links. We use a lot of links to Business Rules, modeled Messages, glossary items and so on.

Same happening on version-controlled packages in EA Full 11 to packages that I does not have checkout. It is an annoying thing. Some packages take minutes to checkout.

Generating HTML reports EA eats many line breaks and joins things in a ugly way.

We are trying version 11 with same bugs (1107).

I use this great tool since Version 6.5.

If I forgot something let me know.

Regards,
Márcio

10

Bugs and Issues / Re: EA Crash by SystemAccessViolation by runReport

« on: June 12, 2014, 05:07:45 am »

This issue (for my case) is fixed in EA 1107.

Regards

Stefan

Unlike Stefan it brakes even in 11.1107 (Trial)
In my case I was generating a RTF or PDF report from a versioned package in TFS.

I tried to checkout the package or generate from a non versioned one but EA still crashes.

I used the Use Case Summary and Use Case Details system templates.

UPDATE: On EA full 11.1107 the problem has gone away.

Regards,
Marcio Monego