What is the technical and practical difference bettween these two:

[Lunatic3]

I guess the first one is not professional, but I want to know the exact technical and practical difference between these two class definisions:

First:
Public Class myClass

Public Shared myString as String

End Class


Second:
Public Class myClass

Private Shared c_myString
Public Shared Property myString() As String
Get
Return c_myString
End Get
Set(ByVal Value As String)
c_myString = Value
End Set
End Property

End Class


Thanx

[Edneeis]

The first one uses a field and the other uses a property. As far as technical difference there isn't a whole lot in this example, but practical there is. You have more control over a property, that is the general answer. I think most developers find it good habit to use properties most of the time.

With a field you have no control over the variables access or validation, creation, or whatnot. It gets even more complex when the property is another class.

[robbedaya]

if you use properties while making an usercontrol or so, you have the properties in the property window if you ad your control to an application. You can add inputcontrol to your "Set property".