Group: Forum Members
Posts: 2K,
Visits: 6.6K
|
Well, I think that its more complicated because everything isn't an object....until its been instantiated. Until then, it's a type (System.Type). I.e. you might have a form EmployeeForm. Really this is a Type, not an object. It's not an object until it's been instantiated. E.g. lets say you have a constructor that accepts an Employee ID, then loads that employees record into the form. Then you allow the user to open the form multiple times, for like five employees. Then you have 5 objects of the type EmployeeForm. Then you can iterate through them, using Application.OpenForms() to access these.
I'm still trying to figure out Reflection myself, so I'm still a bit confused as well. Also, since I need to obfuscate my assemblies, I'm more limited using reflection than I'd like.
|