DEAL John M [mailto:[EMAIL PROTECTED]] wrote:
> Also, > as I mentioned, this behavior is prevalent even if the base > page has all non-abstract methods defined but the class > itself is abstract. Right, the problem is that the *class* is abstract. Like John said, the designer attempts to instantiate the Page class... and of course it can't instantiate an *abstract* class. > I would have thought that the behavior would be to ignore any > of the abstract definitions until compile time (throwing > exceptions where > necessary) and still display the visual elements as usual. It's not the methods causing a problem, it's the class. If you want design-time on this page, you're just going to have to go with John's suggestion of making the methods virtual, raising exceptions at that level and leaving the class as non-abstract. Either that or you can't design the base page. HTH, Drew .NET MVP You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
