>>What happens if you access (or assign) a property for which you didn't write the code? Your example is exactly the best illustration of my objection: you have to write code to achieve default behavior. You access a property, you get its value returned. You assign it, it gets assigned the value passed. Why the know would you have to write code for that?
>>
>>Additionally, what's the syntax for adding a property on the fly?
>
>If I didn't write the code? In that case I will be a consumer of the class and can see its PEMs via Visual Studio's class diagram view (toolbar button as well as on the menu). That works for custom classes as well as those that come as part of the .NET framework. If that is what you meant -- not sure.
>
>Yes, you have to write code. To me it is very easy to do so, as described in an earlier reply, and a small part of the work involved in writing a class. It's not an issue for me at all.

IOW, you can't have a property if there's no code for it, no matter who wrote it? Next thing you'll tell me there are no array properties...

>I don't know how to add a property on the fly. Maybe one of the more experienced .NET developers here knows a way. Personally I'm not sure it's such a good idea. Can you give me an example of when you might want to do that?

Yes. I can. Why do you want one? To give a solution for that particular case using a workaround?

If it's a bad idea, go tell the Fox team that they screwed up :).