I am using reflection to instantiate an object. This works well and I have been using it since four years now.

Basically, I have this code:

        Dim loClass As Type = Nothing
        Dim loList As Framework.Framework.List = Nothing
        Dim loParameter(0) As Object

        loParameter(0) = oProcess

        Try
            loClass = Type.GetType("UniversalThread.ListSomething")
            loList = Activator.CreateInstance(loClass, loParameter)
        Catch loError As Exception
            oProcess.ErrorSetup(loError)
            Return False
        End Try

Then, from this point, I can access the list such as:

loList.ShowList()

But, the problem I can see is the following. At the time loList is created with the Activator, this does not expose the base class properties. So, in my case, I now need to check for a property of the base class before doing loList.ShowList(). Basically, I need to do this:

        Dim loClass As Type = Nothing
        Dim loList As Framework.Framework.List = Nothing
        Dim loParameter(0) As Object

        loParameter(0) = oProcess

        Try
            loClass = Type.GetType("UniversalThread.ListSomething")
            loList = Activator.CreateInstance(loClass, loParameter)
        Catch loError As Exception
            oProcess.ErrorSetup(loError)
            Return False
        End Try

        ' If the list requires administration
        If loList.lAdministrator Then
           ' Do something
        End If

        loList.ShowList()

Because of this type of approach, I cannot see the base class property values. In the particular list I am trying to access, lAdministrator is True. But, it cannot be seen at this point because of the way I have created the object. There might be something I am missing here but I am pretty sure this approach is causing this kind of reaction.