J
JR
I'm developing in VS.NET 2002 and I'm having trouble working around the
issue with page inheritance and the VS.NET Form Designer.
When I create a base class for my form, and inherit from it, I can no longer
bring up the inherited form in the designer. I get the error "The file
failed to load in the Web form designer. please correct the following error,
then load it again : Type Abstract"
Apparently, others have experienced this problem and one workaround is not
declaring the base class as MustInherit.
However, I have a problem with that. My base class handles some processing
in Page_Load. In order to handle some instance-specific handling in the
derived class, I added an Initialize method in the base class and flagged it
as Overridable originally.
If I'm forced to remove the MustInherit and Overridable attributes in my
base class to work around the VS designer issue, then when my code executes,
the Initialize method executes IN THE BASE CLASS, as opposed to in the
derived class. That's not what I want (which is .
I can probably fix this by refactoring the way I'm handing the
initialization, but I'd still like to know if the VS.NET designer issue has
been corrected.
issue with page inheritance and the VS.NET Form Designer.
When I create a base class for my form, and inherit from it, I can no longer
bring up the inherited form in the designer. I get the error "The file
failed to load in the Web form designer. please correct the following error,
then load it again : Type Abstract"
Apparently, others have experienced this problem and one workaround is not
declaring the base class as MustInherit.
However, I have a problem with that. My base class handles some processing
in Page_Load. In order to handle some instance-specific handling in the
derived class, I added an Initialize method in the base class and flagged it
as Overridable originally.
If I'm forced to remove the MustInherit and Overridable attributes in my
base class to work around the VS designer issue, then when my code executes,
the Initialize method executes IN THE BASE CLASS, as opposed to in the
derived class. That's not what I want (which is .
I can probably fix this by refactoring the way I'm handing the
initialization, but I'd still like to know if the VS.NET designer issue has
been corrected.