parsing error: ambiguous match found

Last post 09-24-2009 4:10 PM by mbaladi. 20 replies.

Sort Posts:

  • Re: parsing error: ambiguous match found

    06-04-2007, 1:27 AM
    • Member
      167 point Member
    • Shrikaant
    • Member since 12-18-2006, 3:51 AM
    • Posts 148

    Hi Use the fully qualified name for the  treeview control.

    like Microsoft.Web.UI.WebControl.TreeView.

    This is how i resolved my problem.

  • Re: parsing error: ambiguous match found

    07-09-2007, 2:10 AM
    • Member
      2 point Member
    • herry_squall
    • Member since 07-09-2007, 6:02 AM
    • Posts 1

    I've the same problem with you, better you check the file first. Just simply right click on the file and chose "Convert to web application". If there is still an error, then you must check all control that you've declared in the file.

     

    I assumed there are controls that have the same name even the name are case sensitive

    ie.

    protected System.Web.UI.WebControls.DataGrid DataGrid1;
    protected System.Web.UI.WebControls.DataGrid Datagrid1;

  • Re: parsing error: ambiguous match found

    08-20-2007, 5:21 AM
    Hi, I am facing same problem... I installed the 1.1 development copy on IIS 2.0.... and it gives me same error at line 1.... If i am changing the the Ver to 1.1 the problem resolves.... but this is not the soltuion as many hosting agencies use 2.0 by default... can any one tell me the solution????
    Please MARK post as ANSWERED, if you find answer helpful
    http://www.linkedin.com/in/shantanushukla
  • Re: parsing error: ambiguous match found

    01-10-2008, 11:55 AM

    shantanushukla:
    Hi, I am facing same problem... I installed the 1.1 development copy on IIS 2.0.... and it gives me same error at line 1.... If i am changing the the Ver to 1.1 the problem resolves.... but this is not the soltuion as many hosting agencies use 2.0 by default... can any one tell me the solution????
     

    I got the answer... The problem was I have declared one control twice... after eliminating that dirt code.. my problem resolved 

    Please MARK post as ANSWERED, if you find answer helpful
    http://www.linkedin.com/in/shantanushukla
  • Re: parsing error: ambiguous match found

    07-23-2008, 7:42 PM
    • Member
      7 point Member
    • ajdennis78
    • Member since 09-22-2005, 5:48 AM
    • Posts 2

    This may be obvious to most, but an easy way to find what possible declarations might be overlapping is to do a "find all" within the .aspx.cs page with the search term "new". Go through each line of the search results and figure out the candidates of what controls names might also be used/overlapping on your .aspx page.

  • Re: parsing error: ambiguous match found

    09-24-2009, 4:10 PM
    • Member
      3 point Member
    • mbaladi
    • Member since 05-29-2007, 8:03 AM
    • Posts 2

    IMHO this is a bug and I wish someone could fix it before more people waste time on it! I just wasted a couple of hours to track this down. Turns out that the CreateUserWizard requires me to name a a textbox control UserName and that I had a private variable in a private helper function :-O in the code behind named userName.

Page 2 of 2 (21 items) < Previous 1 2