When and Why use "Me."?

[Richard Thornley]

Hello,

I realize that this is a very basic question but is there an advantage to
using Me.ControlName. Text over just using ControlName.Tex t? I have been
leaving the Me. off but would include it if there are benefits.

Thanks,
Richard

[One Handed Man \( OHM - Terry Burns \)]

Re: When and Why use "Me." ?

Me is a handy reference if you cant remember the object name, intellisense
will give you a list.

--
OHM ( Terry Burns ) * Use the following to email me *

Dim ch() As Char = "ufssz/cvsotAhsfbuTpmv ujpotXjui/OFU".ToCharArra y()
For i As Int32 = 0 To ch.Length - 1
ch(i) = Convert.ToChar( Convert.ToInt16 (ch(i)) - 1)
Next
Process.Start(" mailto:" & New String(ch))
--


"Richard Thornley" <rhek@thorsoft. com> wrote in message
news:evSDyXpsEH A.1180@TK2MSFTN GP10.phx.gbl...[color=blue]
> Hello,
>
> I realize that this is a very basic question but is there an advantage to
> using Me.ControlName. Text over just using ControlName.Tex t? I have been
> leaving the Me. off but would include it if there are benefits.
>
> Thanks,
> Richard
>[/color]

[Cor Ligthert]

Re: When and Why use &quot;Me.&quot; ?

Richard,

Me is mostly just used as an easy shortcut to intelisence, for the rest it
makes no sense with the little exception when there is an ambigious name
used in your program. Than you can use it as well to make that name unique.
I think that a better name had been My. It are all things that directly
belongs to the class. However I am not a person wich native language is
English so I have to be a little bit carefull with telling this.

I hope this helps?

Cor

"Richard Thornley" <rhek@thorsoft. com>
[color=blue]
> Hello,
>
> I realize that this is a very basic question but is there an advantage to
> using Me.ControlName. Text over just using ControlName.Tex t? I have been
> leaving the Me. off but would include it if there are benefits.
>
> Thanks,
> Richard
>[/color]

[Richard Thornley]

Re: When and Why use &quot;Me.&quot; ?

Thank You for the explaination. That is what I thought it was for but
sometimes a simple answer is difficult to find in a manual or book.

Cheers,

Richard

"One Handed Man ( OHM - Terry Burns )" <news.microsoft .com> wrote in message
news:%23lZB2mps EHA.3984@TK2MSF TNGP09.phx.gbl. ..[color=blue]
> Me is a handy reference if you cant remember the object name, intellisense
> will give you a list.
>
> --
> OHM ( Terry Burns ) * Use the following to email me *
>
> Dim ch() As Char = "ufssz/cvsotAhsfbuTpmv ujpotXjui/OFU".ToCharArra y()
> For i As Int32 = 0 To ch.Length - 1
> ch(i) = Convert.ToChar( Convert.ToInt16 (ch(i)) - 1)
> Next
> Process.Start(" mailto:" & New String(ch))
> --
>
>
> "Richard Thornley" <rhek@thorsoft. com> wrote in message
> news:evSDyXpsEH A.1180@TK2MSFTN GP10.phx.gbl...[color=green]
>> Hello,
>>
>> I realize that this is a very basic question but is there an advantage to
>> using Me.ControlName. Text over just using ControlName.Tex t? I have been
>> leaving the Me. off but would include it if there are benefits.
>>
>> Thanks,
>> Richard
>>[/color]
>
>[/color]

[Richard Thornley]

Re: When and Why use &quot;Me.&quot; ?

Thank You for the explaination. That is what I thought it was for but
sometimes a simple answer is difficult to find in a manual or book.

Cheers,

Richard

"Cor Ligthert" <notmyfirstname @planet.nl> wrote in message
news:ODmpuspsEH A.1344@TK2MSFTN GP10.phx.gbl...[color=blue]
> Richard,
>
> Me is mostly just used as an easy shortcut to intelisence, for the rest
> it makes no sense with the little exception when there is an ambigious
> name used in your program. Than you can use it as well to make that name
> unique. I think that a better name had been My. It are all things that
> directly belongs to the class. However I am not a person wich native
> language is English so I have to be a little bit carefull with telling
> this.
>
> I hope this helps?
>
> Cor
>
> "Richard Thornley" <rhek@thorsoft. com>
>[color=green]
>> Hello,
>>
>> I realize that this is a very basic question but is there an advantage to
>> using Me.ControlName. Text over just using ControlName.Tex t? I have been
>> leaving the Me. off but would include it if there are benefits.
>>
>> Thanks,
>> Richard
>>[/color]
>
>[/color]

[CJ Taylor]

Re: When and Why use &quot;Me.&quot; ?

Couldn't Me also be substituted for MyClass?


"One Handed Man ( OHM - Terry Burns )" <news.microsoft .com> wrote in message
news:%23lZB2mps EHA.3984@TK2MSF TNGP09.phx.gbl. ..[color=blue]
> Me is a handy reference if you cant remember the object name, intellisense
> will give you a list.
>
> --
> OHM ( Terry Burns ) * Use the following to email me *
>
> Dim ch() As Char = "ufssz/cvsotAhsfbuTpmv ujpotXjui/OFU".ToCharArra y()
> For i As Int32 = 0 To ch.Length - 1
> ch(i) = Convert.ToChar( Convert.ToInt16 (ch(i)) - 1)
> Next
> Process.Start(" mailto:" & New String(ch))
> --
>
>
> "Richard Thornley" <rhek@thorsoft. com> wrote in message
> news:evSDyXpsEH A.1180@TK2MSFTN GP10.phx.gbl...[color=green]
> > Hello,
> >
> > I realize that this is a very basic question but is there an advantage[/color][/color]
to[color=blue][color=green]
> > using Me.ControlName. Text over just using ControlName.Tex t? I have been
> > leaving the Me. off but would include it if there are benefits.
> >
> > Thanks,
> > Richard
> >[/color]
>
>[/color]

[Rowland Shaw]

RE: When and Why use &quot;Me.&quot; ?

The "me" reference exists so that an object can pass references of itself to
other classes and methods.

using me.member (etc) is handy for Intellisence (as people have already
noted), but it may also speed up compilation time, as the compilier doesn't
have to look through the entire symbol table to resolve the entry.

"Richard Thornley" wrote:
[color=blue]
> Hello,
>
> I realize that this is a very basic question but is there an advantage to
> using Me.ControlName. Text over just using ControlName.Tex t? I have been
> leaving the Me. off but would include it if there are benefits.
>
> Thanks,
> Richard
>
>
>[/color]

[One Handed Man \( OHM - Terry Burns \)]

Re: When and Why use &quot;Me.&quot; ?

Yes, good point MyClass enables you to refer to the current object.

--
OHM ( Terry Burns ) * Use the following to email me *

Dim ch() As Char = "ufssz/cvsotAhsfbuTpmv ujpotXjui/OFU".ToCharArra y()
For i As Int32 = 0 To ch.Length - 1
ch(i) = Convert.ToChar( Convert.ToInt16 (ch(i)) - 1)
Next
Process.Start(" mailto:" & New String(ch))
--


"Richard Thornley" <rhek@thorsoft. com> wrote in message
news:OSscm3psEH A.220@TK2MSFTNG P15.phx.gbl...[color=blue]
> Thank You for the explaination. That is what I thought it was for but
> sometimes a simple answer is difficult to find in a manual or book.
>
> Cheers,
>
> Richard
>
> "Cor Ligthert" <notmyfirstname @planet.nl> wrote in message
> news:ODmpuspsEH A.1344@TK2MSFTN GP10.phx.gbl...[color=green]
>> Richard,
>>
>> Me is mostly just used as an easy shortcut to intelisence, for the rest
>> it makes no sense with the little exception when there is an ambigious
>> name used in your program. Than you can use it as well to make that name
>> unique. I think that a better name had been My. It are all things that
>> directly belongs to the class. However I am not a person wich native
>> language is English so I have to be a little bit carefull with telling
>> this.
>>
>> I hope this helps?
>>
>> Cor
>>
>> "Richard Thornley" <rhek@thorsoft. com>
>>[color=darkred]
>>> Hello,
>>>
>>> I realize that this is a very basic question but is there an advantage
>>> to using Me.ControlName. Text over just using ControlName.Tex t? I have
>>> been leaving the Me. off but would include it if there are benefits.
>>>
>>> Thanks,
>>> Richard
>>>[/color]
>>
>>[/color]
>
>[/color]

[One Handed Man \( OHM - Terry Burns \)]

Re: When and Why use &quot;Me.&quot; ?

Yes, good point MyClass enables you to refer to the current object.

--
OHM ( Terry Burns ) * Use the following to email me *

Dim ch() As Char = "ufssz/cvsotAhsfbuTpmv ujpotXjui/OFU".ToCharArra y()
For i As Int32 = 0 To ch.Length - 1
ch(i) = Convert.ToChar( Convert.ToInt16 (ch(i)) - 1)
Next
Process.Start(" mailto:" & New String(ch))
--


"CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
news:eHq7DBrsEH A.2300@TK2MSFTN GP09.phx.gbl...[color=blue]
> Couldn't Me also be substituted for MyClass?
>
>
> "One Handed Man ( OHM - Terry Burns )" <news.microsoft .com> wrote in
> message
> news:%23lZB2mps EHA.3984@TK2MSF TNGP09.phx.gbl. ..[color=green]
>> Me is a handy reference if you cant remember the object name,
>> intellisense
>> will give you a list.
>>
>> --
>> OHM ( Terry Burns ) * Use the following to email me *
>>
>> Dim ch() As Char = "ufssz/cvsotAhsfbuTpmv ujpotXjui/OFU".ToCharArra y()
>> For i As Int32 = 0 To ch.Length - 1
>> ch(i) = Convert.ToChar( Convert.ToInt16 (ch(i)) - 1)
>> Next
>> Process.Start(" mailto:" & New String(ch))
>> --
>>
>>
>> "Richard Thornley" <rhek@thorsoft. com> wrote in message
>> news:evSDyXpsEH A.1180@TK2MSFTN GP10.phx.gbl...[color=darkred]
>> > Hello,
>> >
>> > I realize that this is a very basic question but is there an advantage[/color][/color]
> to[color=green][color=darkred]
>> > using Me.ControlName. Text over just using ControlName.Tex t? I have been
>> > leaving the Me. off but would include it if there are benefits.
>> >
>> > Thanks,
>> > Richard
>> >[/color]
>>
>>[/color]
>
>[/color]

[Herfried K. Wagner [MVP]]

Re: When and Why use &quot;Me.&quot; ?

"Richard Thornley" <rhek@thorsoft. com> schrieb:[color=blue]
> I realize that this is a very basic question but is there
> an advantage to using Me.ControlName. Text over just
> using ControlName.Tex t? I have been leaving the Me.
> off but would include it if there are benefits.[/color]

Consider this example:

\\\
Private Foo As Integer = 77

Private Function Test() As Integer
Dim Foo As Integer = 99
Return Me.Foo + Foo
End Function
///

;-)

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[rawCoder]

Re: When and Why use &quot;Me.&quot; ?

It can be but you have to note that any method called using MyClass is taken
as Notoverridable as stated in MSDN below.

"
MyClass behaves like an object variable referring to the current instance of
a class as originally implemented. MyClass is similar to Me, but all method
calls on it are treated as if the method were NotOverridable. Therefore, the
method being called is not affected by overriding in a derived class.
"

HTH
rawCoder



"CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
news:eHq7DBrsEH A.2300@TK2MSFTN GP09.phx.gbl...[color=blue]
> Couldn't Me also be substituted for MyClass?
>
>
> "One Handed Man ( OHM - Terry Burns )" <news.microsoft .com> wrote in[/color]
message[color=blue]
> news:%23lZB2mps EHA.3984@TK2MSF TNGP09.phx.gbl. ..[color=green]
> > Me is a handy reference if you cant remember the object name,[/color][/color]
intellisense[color=blue][color=green]
> > will give you a list.
> >
> > --
> > OHM ( Terry Burns ) * Use the following to email me *
> >
> > Dim ch() As Char = "ufssz/cvsotAhsfbuTpmv ujpotXjui/OFU".ToCharArra y()
> > For i As Int32 = 0 To ch.Length - 1
> > ch(i) = Convert.ToChar( Convert.ToInt16 (ch(i)) - 1)
> > Next
> > Process.Start(" mailto:" & New String(ch))
> > --
> >
> >
> > "Richard Thornley" <rhek@thorsoft. com> wrote in message
> > news:evSDyXpsEH A.1180@TK2MSFTN GP10.phx.gbl...[color=darkred]
> > > Hello,
> > >
> > > I realize that this is a very basic question but is there an advantage[/color][/color]
> to[color=green][color=darkred]
> > > using Me.ControlName. Text over just using ControlName.Tex t? I have[/color][/color][/color]
been[color=blue][color=green][color=darkred]
> > > leaving the Me. off but would include it if there are benefits.
> > >
> > > Thanks,
> > > Richard
> > >[/color]
> >
> >[/color]
>
>[/color]

[Mike McIntyre]

Re: When and Why use &quot;Me.&quot; ?

Hi Richard,

The Me keyword is actually required in some situations.

In the example class below, Me is used to disambiguate between Sub New's
lastName parameter and the LastName property. Since the Sub New parameter
is named 'lastName' and the class includes a Property named 'LastName', Me
is necessary to ensure the assignment works correctly. NOTE: If you don't
use Me in this case no error will be generated but assignements will not
always work as expected.

me.LastName = lastName

Public Class Customer
Private _LastName As String

Public Property LastName() As String
Get
Return _LastName
End Get
Set (ByVal value As String)
me._LastName = value
End Set
End Property

Public Sub New(ByVal lastName As String)
me.LastName = lastName
End Sub

Public Sub ChangeLastName( ByVal lastName As String)
me.LastName = lastName
End Sub

End Class

We have a policy at my development company - we always use the Me keyword.
Why?

1. There is no penalty for using Me.

2. Using Me triggers intellisense that reinforces an object-oriented style
of programming. Many authors and experts call Me (and the C# equivalent:
This) the OOP syntax for referring to class members.

3. As shown in the example above, Me is required in some cases.

4. Me improves code readability - one can always tell when a class member is
being used v.s. a local variable, parameter, etc.

--
Mike

Mike McIntyre
Visual Basic MVP

https://www.getdotnetcode.com

"Richard Thornley" <rhek@thorsoft. com> wrote in message
news:evSDyXpsEH A.1180@TK2MSFTN GP10.phx.gbl...[color=blue]
> Hello,
>
> I realize that this is a very basic question but is there an advantage to
> using Me.ControlName. Text over just using ControlName.Tex t? I have been
> leaving the Me. off but would include it if there are benefits.
>
> Thanks,
> Richard
>[/color]

[rawCoder]

Re: When and Why use &quot;Me.&quot; ?

Hi Mike,

Good Explanation,
Just a point.
Can we infer it as a kind of Scope Resolution Operator.

Thank You
rawCoder


"Mike McIntyre" <mikemc@dotnets howandtell.com> wrote in message
news:O$EUYbssEH A.1336@tk2msftn gp13.phx.gbl...[color=blue]
> Hi Richard,
>
> The Me keyword is actually required in some situations.
>
> In the example class below, Me is used to disambiguate between Sub New's
> lastName parameter and the LastName property. Since the Sub New parameter
> is named 'lastName' and the class includes a Property named 'LastName', Me
> is necessary to ensure the assignment works correctly. NOTE: If you[/color]
don't[color=blue]
> use Me in this case no error will be generated but assignements will not
> always work as expected.
>
> me.LastName = lastName
>
> Public Class Customer
> Private _LastName As String
>
> Public Property LastName() As String
> Get
> Return _LastName
> End Get
> Set (ByVal value As String)
> me._LastName = value
> End Set
> End Property
>
> Public Sub New(ByVal lastName As String)
> me.LastName = lastName
> End Sub
>
> Public Sub ChangeLastName( ByVal lastName As String)
> me.LastName = lastName
> End Sub
>
> End Class
>
> We have a policy at my development company - we always use the Me keyword.
> Why?
>
> 1. There is no penalty for using Me.
>
> 2. Using Me triggers intellisense that reinforces an object-oriented style
> of programming. Many authors and experts call Me (and the C# equivalent:
> This) the OOP syntax for referring to class members.
>
> 3. As shown in the example above, Me is required in some cases.
>
> 4. Me improves code readability - one can always tell when a class member[/color]
is[color=blue]
> being used v.s. a local variable, parameter, etc.
>
> --
> Mike
>
> Mike McIntyre
> Visual Basic MVP
> www.getdotnetcode.com
>
>
> "Richard Thornley" <rhek@thorsoft. com> wrote in message
> news:evSDyXpsEH A.1180@TK2MSFTN GP10.phx.gbl...[color=green]
> > Hello,
> >
> > I realize that this is a very basic question but is there an advantage[/color][/color]
to[color=blue][color=green]
> > using Me.ControlName. Text over just using ControlName.Tex t? I have been
> > leaving the Me. off but would include it if there are benefits.
> >
> > Thanks,
> > Richard
> >[/color]
>
>[/color]

[Richard Thornley]

Re: When and Why use &quot;Me.&quot; ?

Mike,

Thanks for the indepth reply and to all the other replys that have been
made. I think I will start using Me. in my coding.

Richard

"Mike McIntyre" <mikemc@dotnets howandtell.com> wrote in message
news:O$EUYbssEH A.1336@tk2msftn gp13.phx.gbl...[color=blue]
> Hi Richard,
>
> The Me keyword is actually required in some situations.
>
> In the example class below, Me is used to disambiguate between Sub New's
> lastName parameter and the LastName property. Since the Sub New parameter
> is named 'lastName' and the class includes a Property named 'LastName', Me
> is necessary to ensure the assignment works correctly. NOTE: If you
> don't use Me in this case no error will be generated but assignements will
> not always work as expected.
>
> me.LastName = lastName
>
> Public Class Customer
> Private _LastName As String
>
> Public Property LastName() As String
> Get
> Return _LastName
> End Get
> Set (ByVal value As String)
> me._LastName = value
> End Set
> End Property
>
> Public Sub New(ByVal lastName As String)
> me.LastName = lastName
> End Sub
>
> Public Sub ChangeLastName( ByVal lastName As String)
> me.LastName = lastName
> End Sub
>
> End Class
>
> We have a policy at my development company - we always use the Me keyword.
> Why?
>
> 1. There is no penalty for using Me.
>
> 2. Using Me triggers intellisense that reinforces an object-oriented style
> of programming. Many authors and experts call Me (and the C# equivalent:
> This) the OOP syntax for referring to class members.
>
> 3. As shown in the example above, Me is required in some cases.
>
> 4. Me improves code readability - one can always tell when a class member
> is being used v.s. a local variable, parameter, etc.
>
> --
> Mike
>
> Mike McIntyre
> Visual Basic MVP
> www.getdotnetcode.com
>
>
> "Richard Thornley" <rhek@thorsoft. com> wrote in message
> news:evSDyXpsEH A.1180@TK2MSFTN GP10.phx.gbl...[color=green]
>> Hello,
>>
>> I realize that this is a very basic question but is there an advantage to
>> using Me.ControlName. Text over just using ControlName.Tex t? I have been
>> leaving the Me. off but would include it if there are benefits.
>>
>> Thanks,
>> Richard
>>[/color]
>
>[/color]

[Mike McIntyre]

Re: When and Why use &quot;Me.&quot; ?

Not in the strictest sense; it does not qualify a namespace member to its
namespace the way a C++ scope resolution operator is used to qualify a
namespace member to its namespace.

The Me keyword refers to the current instance of the class and so all
members of the current instance can be referenced through it.

FYI the scope resolution operators for Microsoft programming languages:

Visual Basic Visual J# C++ C# JScript Visual FoxPro
Scope resolution
Scope resolution . n/a :: . and base n/a ::


--
Mike

Mike McIntyre
Visual Basic MVP

https://www.getdotnetcode.com

"rawCoder" <rawCoder@hotma il.com> wrote in message
news:OkjNFxtsEH A.1924@TK2MSFTN GP10.phx.gbl...[color=blue]
> Hi Mike,
>
> Good Explanation,
> Just a point.
> Can we infer it as a kind of Scope Resolution Operator.
>
> Thank You
> rawCoder
>
>
> "Mike McIntyre" <mikemc@dotnets howandtell.com> wrote in message
> news:O$EUYbssEH A.1336@tk2msftn gp13.phx.gbl...[color=green]
>> Hi Richard,
>>
>> The Me keyword is actually required in some situations.
>>
>> In the example class below, Me is used to disambiguate between Sub New's
>> lastName parameter and the LastName property. Since the Sub New
>> parameter
>> is named 'lastName' and the class includes a Property named 'LastName',
>> Me
>> is necessary to ensure the assignment works correctly. NOTE: If you[/color]
> don't[color=green]
>> use Me in this case no error will be generated but assignements will not
>> always work as expected.
>>
>> me.LastName = lastName
>>
>> Public Class Customer
>> Private _LastName As String
>>
>> Public Property LastName() As String
>> Get
>> Return _LastName
>> End Get
>> Set (ByVal value As String)
>> me._LastName = value
>> End Set
>> End Property
>>
>> Public Sub New(ByVal lastName As String)
>> me.LastName = lastName
>> End Sub
>>
>> Public Sub ChangeLastName( ByVal lastName As String)
>> me.LastName = lastName
>> End Sub
>>
>> End Class
>>
>> We have a policy at my development company - we always use the Me
>> keyword.
>> Why?
>>
>> 1. There is no penalty for using Me.
>>
>> 2. Using Me triggers intellisense that reinforces an object-oriented
>> style
>> of programming. Many authors and experts call Me (and the C# equivalent:
>> This) the OOP syntax for referring to class members.
>>
>> 3. As shown in the example above, Me is required in some cases.
>>
>> 4. Me improves code readability - one can always tell when a class member[/color]
> is[color=green]
>> being used v.s. a local variable, parameter, etc.
>>
>> --
>> Mike
>>
>> Mike McIntyre
>> Visual Basic MVP
>> www.getdotnetcode.com
>>
>>
>> "Richard Thornley" <rhek@thorsoft. com> wrote in message
>> news:evSDyXpsEH A.1180@TK2MSFTN GP10.phx.gbl...[color=darkred]
>> > Hello,
>> >
>> > I realize that this is a very basic question but is there an advantage[/color][/color]
> to[color=green][color=darkred]
>> > using Me.ControlName. Text over just using ControlName.Tex t? I have been
>> > leaving the Me. off but would include it if there are benefits.
>> >
>> > Thanks,
>> > Richard
>> >[/color]
>>
>>[/color]
>
>[/color]