"Christian Falch" <chris@nowhere.com> wrote in message
news:uUKPb415DHA.3476@tk2msftngp13.phx.gbl...
> Hi,
>
> Anthony Ruggeri wrote:
> > I've heard a little bit about the "ambiguous match found" problem with
> > VB.Net custom controls. We suddenly started getting this error
yesterday.
> > We are running ASP.NET 1.1 and using Visual Studio 2003.
> >
> > Has anyone else seen this error and (better yet) a solution? I heard
that
> > it was fixed in 1.1 but it obviously is not.
>
> I saw it yesterday, and fixed it yesterday as well.
>
> The reason behind why I experienced the error message can be described
> with the following scenario:
>
> I've got two classes; MyBaseClass and MyDerivedBaseClass. Both has a
> property called ParentBaseControl which is returns an instance of
> MyBaseClass in MyBaseClass controls, and is overridden by the keyword
> "new" in the class MyDerivedBaseClass:
>
> public class MyBaseClass
> {
> public MyBaseClass ParentBaseControl...
> }
>
> public class MyDerivedBaseClass: MyBaseClass
> {
> public new MyDervivedBaseClass ParentBaseControl...
> }
>
> When using reflection to set the property ParentBaseControl, I get the
> error message you described, since reflection can't decide which of the
> two properties to use (which is correct, since both are accessible in
> the derived class: the parent class' property can be set with
> base.ParentBaseControl = value).
>
> The solution was simply to give the property a different name in the
> derived class.
>
> Hope this helps!
>
> --
> Chris

Anthony Ruggeri wrote:
> I've heard a little bit about the "ambiguous match found" problem with
> VB.Net custom controls. We suddenly started getting this error yesterday.
> We are running ASP.NET 1.1 and using Visual Studio 2003.
>
> Has anyone else seen this error and (better yet) a solution? I heard that
> it was fixed in 1.1 but it obviously is not.

Anthony Ruggeri wrote:
> Unfortunately changing the name of the property is not really an option,
> since the idea is that derived classes will expose the same interface as is
> found in the base class.

> Plus we are using VB.NET, not C#.