Visual Basic

cleako wrote:

Is that just a programming style or is there more to it than that?

Public Class SomeClass
 
    Private x As Integer
 
    Public Property X() As Integer
        Get
            Return Me.x
        End Get
        Set(ByVal value As Integer)
            Me.x = value
        End Set
    End Property
End Class

Dave Kreskowiak wrote:

Some people overuse it to death, putting Me. in front of everything, making the code painfully to read, even more so in the C# world with this

Dave Kreskowiak wrote:

It just makes your code easier to read in certain situations by taking away some abiguity, like in Property methods

'Requires a propertygrid
Public Class Form1
    Dim test As New TestEnum

    Private Sub Form1_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
        PropertyGrid1.SelectedObject = test
    End Sub
End Class

Public Class TestEnum
    Dim _TestMyEnum As MyEnum

    'This works just fine because we have declared the property as MyEnum
    Public Property TestMyEnum() As MyEnum
        Get
            Return _TestMyEnum
        End Get
        Set(ByVal value As MyEnum)
            _TestMyEnum = value
        End Set
    End Property

    'This returns the exact same enumerator but has been declared as a general object
    'The same problem occurs here as you are seeing in your code
    Public Property TestMyEnumObject() As Object
        Get
            Return _TestMyEnum
        End Get
        Set(ByVal value As Object)
            _TestMyEnum = value
        End Set
    End Property

    Public Enum MyEnum
        Test0
        Test1
        Test2
    End Enum
End Class