Re: Odd behavior in 2005 with base page classes

Hi Craig,

Ah yes, the pain of upgrading real world projects <g>...

The issues you are encountering are due to the fact that ASP.NET changes the
way page inheritance works in 2.0. Add to that the abstraction that the
Conversion Wizard adds and you end up with some cases where you get errors
like you're experiencing.

Now in your case the properties happen to be ASP.NET internal properties. Do
you really have these properties implemented somewhere in your page
hierarchy? Profile is a new ASP.NET property on the page class so if you had
an existing Profile property there will be a conflict. This may not be a
problem and you can simply add the New keyword as described. But if you do
have a conflict then your only choice will be to rename...


+++ Rick --

--

Rick Strahl
West Wind Technologies
www.west-wind.com
www.west-wind.com/weblog


<craig.wagner@xxxxxxxxx> wrote in message
news:1132944934.830694.122370@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>I have converted two ASP.NET 1.1 applications to ASP.NET 2.0. Each one
> had some odd results, most of which I've been able to address. I'm
> looking for some confirmation/advice.
>
> Both applications use a base page class inherited from
> System.Web.UI.Page. In both cases my base page class is in a separate
> folder of the web application (e.g. c:\mywebapp\baseclass).
>
> When I converted the second application, the wizard was insistent on
> creating an abstract stub for my base class, which messed everything up
> royally (circular reference errors). I unwound that. The wizard seems a
> little indiscrimanent about applying that particular coding pattern to
> my applications, btw.
>
> Anyway, upon first trying to compile my app I got errors that it
> couldn't find my base page class. I resolved that by adding the
> following to each page that complained about not finding the base
> class.
>
> <%@ Reference Page="~/BaseClasses/basepage.aspx" %>
>
> Everything is now compiling without error, but I am getting a lot of
> warnings like the following.
>
> Warning 2 'Nwea.BlueWater.GenericError.Profile' hides inherited
> member 'Nwea.BlueWater.BaseClasses.BasePage.Profile'. Use the new
> keyword if hiding was intended.
> c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> Files\bluewateradmin\4c8ac349\b294ab7\App_Web_rga8akwb.0.cs 45
> Warning 3 'Nwea.BlueWater.GenericError.ApplicationInstance' hides
> inherited member
> 'Nwea.BlueWater.BaseClasses.BasePage.ApplicationInstance'. Use the new
> keyword if hiding was intended.
> c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> Files\bluewateradmin\4c8ac349\b294ab7\App_Web_rga8akwb.0.cs 51
>
> I only get these in one of my converted projects, not the other (and
> they both use a base page class). The problem is that the warning is
> showing up in files that are being generated for me.
>
> Any thoughts/suggestions/pointers?
>


.

Relevant Pages

  • RE: Inherited web.config ASP.NET 2.0
    ... And those ASP.NET 2.0 web applications ... describe the general rules of such configuration inheritance: ... through a physical sub directory or a mapped external ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: public inheritance of interfaces and virtual (multiple) inheri
    ... I will not cling to the death to use virtual inheritance. ... However, in MFC, you need to declare a pointer to a member of a class ... we can end up corrupting pointers. ... There is a warning, ...
    (microsoft.public.vc.language)
  • Re: Suppress warning
    ... Use of inherited AUTOLOAD for non-method main::c2fis deprecated at ... Is there a way to identify the category of warning so I can suppress it ... currently issues an optional warning when non-methods ... Inheritance will not work when ...
    (comp.lang.perl.misc)
  • Re: public inheritance of interfaces and virtual (multiple) inheritanc
    ... I would like to use public inheritance ... Particularly, I have 2 abstract base interface classes, ... There is a warning, ... Pointers to member functions became 16 byte. ...
    (microsoft.public.vc.language)
  • Re: Message Map with multiple inheritance
    ... What should the implementation of the timer function look like? ... The warning indicates the two do not agree. ... or CObject then there should be no inheritance issues - this is likely a red ... > And the WM_TIMER gives me a compiler error of: ...
    (microsoft.public.vc.mfc)