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
|
If I have my Public Entity 'Cats' (Name, LivesRemaining etc.), and create another Entity 'FavouriteFood' (Make, Tastiness etc.) with a One-One association, all works fine - Lightspeed auto-generates the property 'FavouriteFood' and everything works as expected. But if I mark FavouriteFood as Internal, then the compiler fails because the property on Cats is still public. There doesn't seem any way to change it. It it possible? Thanks. |
|
|
|
|
No, this looks like an issue that we are not exposing those controls for you on One to One relationships (e.g. you can control the Collection/Backreference visibility on One to Many associations which allows you to handle this). I will add in controls for this and let you know once this is available in the nightlies. In the meantime if you need to work around this you can change the "Generation" property on the association to FieldOnly and then implement the properties manually in partial classes for each type. Whats probably easiest for that is to copy and paste the existing code into partials before you switch the Generation flag and then fix up the visibility modifier on Cats afterwards.
|
|
|
|
|
Just an update to let you know that I have added this in for tonights nightly build so you should be able to pick that up later prior to having to use the workaround :)
|
|
|
|
|
Thanks very much, excellent support as usual. |
|
|
|
