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
|
The (non-designer) C# quickstart shows how to add EntityHolder and EntityCollection attributes in order to implement a many-to-one/one-to-many association. But should these attributes not be private? Specifically in the following two lines, I think that "public" should be "private". Am I wrong? public EntityHolder<Member> _contributor = new EntityHolder<Member>(); |
|
|
Technically, they can be public or private, but you're right: private would be (much!) better style. Thanks for alerting us to this! |
|
|
Hi Frank, Good spotting :) Yes, normally they should be private, the reason they are not in this case is that they code snippets are directly sourced from our tests model, and some of our tests access those underlying collection fields directly, hence their need to be public in this case. That said, we can probably look to tidy this up as its likely to cause confusion - thanks for pointing this out, we can have a look to see if we can base this on a seperate part of the test model :)
Jeremy |
|