Thank you, Ian.
Based upon your excellent and thorough examination of this subject, I've
decided to continue using Reflection, and not get sidetracked with the
nuances of Property/Event Descriptors.
If the need arises to extend or hide members, I'll reconsider. For now, the
requirements are simpl
"Not that I have any intention of using this... Needing a whole separate
assembly is rather inconvenient, and it feels like an abuse of the
underlying mechanism. But I think you knew that..."
I know ... The separate assembly during compilation appears to be
unavoidable, but there might be a way
Fernando,
Thanks for your details explanation! I actually did play with security
policy when I was studying CAS and related things, but since that I
reinstalled my computer (when h/w upgraded), so now it is default.
However I double checked the policy and it is Unrestricted,
My_Computer_Zone and a
Fabian,
I think you need to use ISerializable and IObjectReference on a helper
class. The trick is described here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemruntimeserializationiserializableclassgetobjectdatatopic.asp
Alexander
On Mon, 17 Jan 2005 1
Cool - that's exactly the kind of obscure detail I was hoping for!
Not that I have any intention of using this... Needing a whole separate
assembly is rather inconvenient, and it feels like an abuse of the
underlying mechanism. But I think you knew that...
Of course a wholly less practical solu
Actually, if you look more carefully you'll see that Steve's right -
System.ComponentModel *does* provide a set of facilities that do provide
very similar services to those available through reflection. (They are
a subset - reflection is more powerful. But it's simply not accurate to
say that "Sy
