The problem is that there is now a "Treeview" control built-into ASP.NET 2.0 -- and so this user control class name is conflicting with it. Can you try renaming your control (specifically the class name)? That should fix it.
I changed the class name and the control name, but I still got the same error:
Parser Error
Description:
An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Ambiguous match found.
Source Error:
Line 1: <%@ Register TagPrefix="uc1" TagName="TabControl" Src="../TabControl.ascx" %>
Line 2: <%@ Register TagPrefix="uc1" TagName="MyTreeView" Src="../MiscControls/Tree/TreeViewWRC.ascx" %>
Line 3: <%@ Page language="c#" Codebehind="TeamApproval.aspx.cs" AutoEventWireup="false" Inherits="WRC.ProjAcct.AspClient.TeamApproval.TeamApproval"%>
The additional information for this error: no matter what the first line was ( blank line, or any line in this aspx file), the same error occured.
Actually, since the migration done, there have been raising new errors. The old version works well, but the new version trouble us lot. We are using WEb Application Project that we downloaded two months ago, we are wondering if installion of the its latest
version will help.
I think the class name conflict is coming from within the .ascx file -- can you check to see what the class name of the .ascx file is? I think you need to rename if from being TreeView.
I'd definitely recommend installing the latest version of WAP. It fixes many issues, and has much better migration support. This walkthrough shows how to migrate from VS 2003 with it:
http://webproject.scottgu.com/CSharp/Migration/Migration.aspx
I did rename the user control's name (TreeView to TreeViewABC), but it did not work. We have another .aspx page that is with almost same content as this .aspx page (also has the TreeView Control), and it works well. Does the conflict(s) exist in this .aspx
page or the .ascx files that <@ registered in this page or any other files? When we did the migration, there were some errors, "ambiguous match found" related to TreeView and TreeNode, during compiling, and after adding the full namespace, the errors disappeared.
Now they work well except this page.
I checked all the controls included in this page, but still have no clue.
Do you have any idea?
Another question, should we redo the migration against the new version Web Application Project?
It might make sense to try it using the WAP project model and see if this helps. Please let me know if you are still running into the ambiguous error message -- if so I can put you in contact with someone to help.
What do you mean "WAP project model" here? We Downloaded and installed the Web Aplication project and migrated our solution according your instruction. This web project was web application project in vs 2003. If this doesn't mean "using WEB project model",
could you sow me in detail how to use WEB project model?
If it's a Web Application Project, check your TeamApproval.ascx.cs and TeamApproval.ascx.designer.cs if they don't contain the same protected member. I got this error and I solved it by deleting 1 protected member from the TeamApproval.ascx.cs, as it was
already in the TeamApproval.ascx.designer.cs file..
newliya
Member
136 Points
65 Posts
parsing error: ambiguous match found
Apr 18, 2006 05:03 PM|LINK
The web application was migrated from 2003 to 2005. When I tryied to open one page, I got the error:
Parser Error Message: Ambiguous match found.
Source Error:
Source File: /xpede.net/TeamApproval/TeamApproval.aspx Line: 1
Could somebofay has any idea?
Thanks a lot!
Liya
ScottGu
All-Star
18320 Points
2008 Posts
Microsoft
Moderator
Re: parsing error: ambiguous match found
Apr 19, 2006 07:27 AM|LINK
Hi Liya,
The problem is that there is now a "Treeview" control built-into ASP.NET 2.0 -- and so this user control class name is conflicting with it. Can you try renaming your control (specifically the class name)? That should fix it.
Thanks,
Scott
newliya
Member
136 Points
65 Posts
Re: parsing error: ambiguous match found
Apr 19, 2006 03:00 PM|LINK
Thanks for your reply.
I changed the class name and the control name, but I still got the same error:
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Ambiguous match found.
Source Error:
Source File: /xpede.net/TeamApproval/TeamApproval.aspx Line: 1
What do you think the possible causes are?
Thanks a lot,
Liya
newliya
Member
136 Points
65 Posts
Re: parsing error: ambiguous match found
Apr 19, 2006 08:20 PM|LINK
Hi Scott,
The additional information for this error: no matter what the first line was ( blank line, or any line in this aspx file), the same error occured.
Actually, since the migration done, there have been raising new errors. The old version works well, but the new version trouble us lot. We are using WEb Application Project that we downloaded two months ago, we are wondering if installion of the its latest version will help.
Thanks a lot,
Liya
ScottGu
All-Star
18320 Points
2008 Posts
Microsoft
Moderator
Re: parsing error: ambiguous match found
Apr 19, 2006 11:10 PM|LINK
Hi Liya,
I think the class name conflict is coming from within the .ascx file -- can you check to see what the class name of the .ascx file is? I think you need to rename if from being TreeView.
I'd definitely recommend installing the latest version of WAP. It fixes many issues, and has much better migration support. This walkthrough shows how to migrate from VS 2003 with it: http://webproject.scottgu.com/CSharp/Migration/Migration.aspx
Hope this helps,
Scott
newliya
Member
136 Points
65 Posts
Re: parsing error: ambiguous match found
Apr 20, 2006 05:03 PM|LINK
Hi Scott,
I did rename the user control's name (TreeView to TreeViewABC), but it did not work. We have another .aspx page that is with almost same content as this .aspx page (also has the TreeView Control), and it works well. Does the conflict(s) exist in this .aspx page or the .ascx files that <@ registered in this page or any other files? When we did the migration, there were some errors, "ambiguous match found" related to TreeView and TreeNode, during compiling, and after adding the full namespace, the errors disappeared. Now they work well except this page.
I checked all the controls included in this page, but still have no clue.
Do you have any idea?
Another question, should we redo the migration against the new version Web Application Project?
Thanks a lot,
Liya
ScottGu
All-Star
18320 Points
2008 Posts
Microsoft
Moderator
Re: parsing error: ambiguous match found
Apr 22, 2006 06:26 PM|LINK
Hi Liya,
It might make sense to try it using the WAP project model and see if this helps. Please let me know if you are still running into the ambiguous error message -- if so I can put you in contact with someone to help.
Thanks,
Scott
newliya
Member
136 Points
65 Posts
Re: parsing error: ambiguous match found
Apr 24, 2006 01:18 PM|LINK
HI Scott,
Thanks for your reply.
What do you mean "WAP project model" here? We Downloaded and installed the Web Aplication project and migrated our solution according your instruction. This web project was web application project in vs 2003. If this doesn't mean "using WEB project model", could you sow me in detail how to use WEB project model?
Thanks alot,
Liya
deyanp
Member
5 Points
1 Post
Re: parsing error: ambiguous match found
Apr 24, 2006 02:01 PM|LINK
If it's a Web Application Project, check your TeamApproval.ascx.cs and TeamApproval.ascx.designer.cs if they don't contain the same protected member. I got this error and I solved it by deleting 1 protected member from the TeamApproval.ascx.cs, as it was already in the TeamApproval.ascx.designer.cs file..
Br,
Deyan
newliya
Member
136 Points
65 Posts
Re: parsing error: ambiguous match found
Apr 25, 2006 01:33 PM|LINK
Thanks, Deyan. This is a very good clue.
Liya