True, with properties, changes can be completed maintaining binary compatibility. But really how often do you have an assembly where binary compatibility is actually an issue? Sometime sure, but I'm thinking it's more often the exception than the rule.
Adding properties in later maintains source compatibility, and generally I've found that's more than enough. Jeff -----Original Message----- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Mark Hurd Sent: Wednesday, 25 August 2010 9:28 AM To: ozDotNet Subject: Re: Properties The thing with properties is that once you have them, changes can be completed without changing the interface, including the binary compatibility of public interfaces. Nevertheless, if your class of variables is not public I too would consider just using fields. -- Regards, Mark Hurd, B.Sc.(Ma.)(Hons.) On Wed, Aug 25, 2010 at 10:43 AM, Jeff Sinclair <jeff.sinclair.em...@gmail.com> wrote: > Can some one tell me why people get so worked up about all fields > being private and accessed only via properties. > > If you have a class which is only used essentially as group of > variables, eg to put into a data structure like a tree or something > then why not public fields? > > Do all those properties really add any value? > > Jeff
