Automatic Properties in C#

[MylesRip]

The new-ish "automatic properties" feature of the C# language seems to stump EA.  It doesn't seem to recognize that a property defined with no explicit underlying field can still represent a relationship between two classes.  Is there currently a way around this?  Does Sparx intend to support this in the future?  If so, when might that be?  

[son-of-sargasso]

  The same day microsoft releases a bug free secure operating system.    

No, don't shoot me I'm innocent I tell you.

[MylesRip]

Ouch.  I've been using EA for about five years now and have never had a reason to consider moving away from it.  The quality of the product and the support has been phenomenal.  

However, if it can't understand language constructs that are likely to get lots of use, that could change very quickly.  (The same goes for being able to recognize relationships that use generic collections - a feature that I use extensively.)  I'm certainly not going to tell developers that they can't use automatic properties.  This could be a real show-stopper for me!  

[Makulik]

Hi Myles,

Send an official feature request to Sparx then.

IMHO having a class property, referring to another class, always results in a relationship between the participating class elements. No matter if there's an underlying field or not.

WBR
Günther

[MylesRip]

I'll do that...  I know it might seem like a little thing, but it ends up having a major impact on the usefulness of the product in a C# environment.  I suspect I'm not the only one who feels that way.