It's easier to change a non-needed property into a useful property than a public field into a useful property, because doing so, will break code. but there are a few things that fields can do that properties can't. It's easier to learn it from the old school, than wait somebody to tell you all.
I can help a lit. more: http://www.codeproject.com/KB/cs/PropertyversusField.aspx --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://cm.megasolutions.net/forums/default.aspx -~----------~----~----~----~------~----~------~--~---
