private variable vs. actual property in a class module?

[SteveS]

What's the difference in using the private variable as opposed to the actual
property in a class module? Which is better or more efficient? (
LoginObject.Sav e (_loginName) or LoginObject.Sav e (me.LoginName)

FOR EXAMPLE:

Class MyClass

Private _loginName As String
Public Property LoginName() As String
Get
Return _loginName
End Get
Set(ByVal Value As String)
_loginName = Value.ToLower()
End Set
End Property

public sub Save()
dim LoginObject as new Data.LoginObjec t
'****** what is the difference in these 2 lines? *******
LoginObject.Sav e (_loginName)
LoginObject.Sav e (me.LoginName)
'************** *************** *************
end function

End Class
Thank You,

SteveS

[Jan Tielens]

I don't think it makes any difference the JIT will optimize the Me.LoginName
so there won't be any performance difference.

In my opinion using the property (Me.LoginName) is advisable, because in
that case you're using OO encapsulation.

--
Greetz

Jan Tielens
_______________ _______________ __
Read my weblog: http://weblogs.asp.net/jan
"SteveS" <ss*****@trendm ls.com> wrote in message
news:eu******** ******@TK2MSFTN GP09.phx.gbl...

What's the difference in using the private variable as opposed to the actual property in a class module? Which is better or more efficient? (
LoginObject.Sav e (_loginName) or LoginObject.Sav e (me.LoginName)

FOR EXAMPLE:

Class MyClass

Private _loginName As String
Public Property LoginName() As String
Get
Return _loginName
End Get
Set(ByVal Value As String)
_loginName = Value.ToLower()
End Set
End Property

public sub Save()
dim LoginObject as new Data.LoginObjec t
'****** what is the difference in these 2 lines? *******
LoginObject.Sav e (_loginName)
LoginObject.Sav e (me.LoginName)
'************** *************** *************
end function

End Class
Thank You,

SteveS