This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Could an option for the generation of a private setter (instead of a public one) be included in the property visibility options? This would allow properties who should be read only (at least publicly) but are still persisted to the database (unlike LoadOnly). For example, if you have a class that takes arguments in in its constructor but then doesn't allow their modification. This could be done with FieldOnly and a partial class, but it seems like a trivial option to add, and would save a lot of custom coding. |
|
|
|
|
Thanks for the suggestion - I have added in a separate option for this to operate as suggested. I am thinking about changing this in the future to make it more of a generic visibility drop-down rather than focusing purely on "private set" but for now it operates as advertised and Ill wait to get some more feedback on this before deciding on if it needs any further work.
|
|
|
|
