On properties (and relation-properties) we have the Modifier setting, which can be configured as Public, Private, Protected, etc.
The problem with that, is that in C# we actually have two access-modifiers, one for the get-method and one for the set-method.
About 75% of the time, these are probably going to be identical - but I have many cases (in an existing model I'm currently rebuilding in ED) where the get-method has a lower access-modifier, e.g. public get and protected set.
To properly support C# accessors, we need something like a SetModifier setting - this could be left empty (or have an additional option called "Same") and by default would use the Modifier setting for the most common cases where both methods have the same access-modifier...
missing feature: set-method access-modifier
New version of Entity Developer 4.2.110 is released!
It can be downloaded from http://www.devart.com/entitydeveloper/download.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=23135 .
It can be downloaded from http://www.devart.com/entitydeveloper/download.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=23135 .
This works, but only for regular properties - please, could you add this feature for navigation properties, too?
(wondering what your implementation looks like - I would have assumed you have a common base-class for properties and navigation-properties, but I'm starting to think you don't? Documentation for navigation properties was also a miss. It seems like both are properties and they have a lot of things in common - maybe it's time to think about some refactoring to provide more consistency in the model? in C# and NH, navigation and regular properties have many, if not most, things in common...)
(wondering what your implementation looks like - I would have assumed you have a common base-class for properties and navigation-properties, but I'm starting to think you don't? Documentation for navigation properties was also a miss. It seems like both are properties and they have a lot of things in common - maybe it's time to think about some refactoring to provide more consistency in the model? in C# and NH, navigation and regular properties have many, if not most, things in common...)
This feature is available in the latest 4.2.120 build of Entity Developer.mindplay wrote: This works, but only for regular properties - please, could you add this feature for navigation properties, too?
The new build can be downloaded from http://www.devart.com/entitydeveloper/download.html (the trial and free versions) or from Registered Users' Area (provided that you have an active subscription).
For more information, please refer to http://www.devart.com/forums/viewtopic.php?t=23252 .