Re: Specify member scope in Interface Classes
aaronh64_at_hotmail.com
Date: 12/30/04
- Next message: Moe Green: "Re: How much is Bill worth right now?"
- Previous message: Chris, Master of All Things Insignificant: "Re: VS .NET 2002 Remove and Reinstall"
- In reply to: Marina: "Re: Specify member scope in Interface Classes"
- Next in thread: Mattias Sjögren: "Re: Specify member scope in Interface Classes"
- Messages sorted by: [ date ] [ thread ]
Date: 30 Dec 2004 14:28:32 -0800
Thanks for your reply Marina,
Yes, you are correct, I could cast the object and access the methods
then, but I think you are missing my point. Microsoft achieved the
behavior that I originally posted, and that's what I'm after. How did
they do it? They were somehow able to define the methods as abstract,
or at least have the WebControl define the methods and then hide them.
Furthermore, what if you want inheriting classes that implement the
interface to be able to override that functionality?
- Next message: Moe Green: "Re: How much is Bill worth right now?"
- Previous message: Chris, Master of All Things Insignificant: "Re: VS .NET 2002 Remove and Reinstall"
- In reply to: Marina: "Re: Specify member scope in Interface Classes"
- Next in thread: Mattias Sjögren: "Re: Specify member scope in Interface Classes"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|