Where is the "Property" template???

[pocketom]

Transformation Templates -> C# -> Attribute__Property

It points to a template "Property" in the last line.

Code: [Select]

%if classStereotype=="enumeration"%
%endTemplate%

$type=%CONVERT_TYPE("C#",attType)%
%Property(attName,$type)%This template isn't availble from the list of templates. When I try to "Add a new custom" template called "Property", I get:

'A template with that name already exists'


Is it hardcoded? I need to edit that to finally add a"virtual" tag when the property operations are created 

[pocketom]

Please respond ASAP, I need to know if I can access that template somehow or not. I'm running out of time!

[pocketom]

The problem seems also to apply to the C# code generation. I cannot find where the property code is generated. The only thing I find are templates Property, Property Declaration, Property Notes, but there I cannot identify any line that generates the code I see in the output (return ..., value = ...), only some EASL_GET() methods that seem to hide what's behind.

Seems that the code generation template behind also cannot be accessed??? What's wrong with those properties, why keeping the generation logic hidden from the EA users? And why isn't that mentioned in the documentation?

[pocketom]

Problem is related to: http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1269599507

[pocketom]

No Ideas? Perhaps the thread should be closed as properties seem to be created by god and he won't answer here ;-)

[Makulik]

Just to have someone else writing on this thread here   ...
Yes it seems that property handling for C# code generation doesn't work very well, I've seen several threads about this topic.
Getter / setter code generation based on the <<property>> stereotype for C++ classes doesn't work well for me also  :-/. I'm simply not using the <<property>> stereotype, though it would be the right thing to apply. But to get properties right in C#, you'll need to use it, fiddly   ...

WBR
g.

[Nizam Mohamed]

Pocketom

unfortunately there was an issue with "Property" transformation template which has now been fixed.

W.r.t Code generation templates, the  "Operation Declaration" "property" stereotype override renders the C# properties.(the Property, Property Declaration, Property Notes are all behavioral code generation specific templates to handle UML properties)

To ensure readily compilable code for C# classes(with Properties),
Please ensure you check the "Capitalized Attribute Name for Properties" option in Code Options.
This will create distinct names for attributes and the associated Properties.

[Nizam Mohamed]

As an interim workaround for "Property" transformation template, you might as well Add New Custom Template with a different name and use the following code

Code: [Select]

$attName=$parameter1
$type=$parameter2
$propertyName=$attName
$propertyName=%REMOVE_PREFIX($propertyName,genOptPropertyPrefix)%
%if genOptGenCapitalisedProperties=="T"%
$propertyName=%CONVERT_NAME($propertyName, "camel case", "pascal case")%
%endIf%
Operation
{
  %TRANSFORM_REFERENCE()%
  name=%qt%$propertyName%qt%
  stereotype="property"
  scope="Public"
  type=%qt%$type%qt%
  Tag{name="attribute_name" value=%qt%$attName%qt%}
}
and also update the "Attribute__Property" template to use that.

This should work the same and there should be no issues with synchronization, etc.
(NB: Enable "Capitalized Attribute Name for Properties"  to ensure compilable code generation)

[pocketom]

Hi, thanx to all for your answers. I'll try out the fix you provided soon.

I also got an answer from the support team:

We can confirm this as an issue that the "Property" template is not currently accessible from the transformation template editor.  This is currently scheduled to be resolved in the next build of Enterprise Architect 8 (build 856).