Thread: class name is ambiguous

Yeah, I saw that article when I googled it, but just understood what was done. Changing Capital to Lower case.

I think I posted the solution in another thread I had open, but thought I'd post it here incase anyone googles the problem. It related to classes that were contained in custom controls that were declared in the page.

I noticed that AJAX added a control declaration in the web.config and I think that caused a conflict with the controls I was declaring within the page. When I declared custom controls in the page directly, I think it was creating multiple instances of the same class, hence the ambigouity.

To solve this issue, I added my custom control declarations into my web.config under <system.web> <pages> <controls>

Code:

<system.web>
   <pages>
       <controls>
          <add tagPrefix="atlas" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
          <add tagPrefix="ajaxtoolkit" assembly="AjaxControlToolkit" namespace="AjaxControlToolkit" />
          <add tagPrefix="mytag" tagName="mytagname" src="~/UserControls/mycontrol.ascx" />
        </controls>
    </pages>
.
.
.
.
.
.
</system.web>

Hope that helps someone.