Asp.net Runtime Error Ambiguos Match Found

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the ambiguous match found c# workings and policies of this site About Us Learn more about Stack

System.reflection.ambiguousmatchexception Ambiguous Match Found

Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs ambiguous match found getproperty Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join ambiguous match found deserialize json them; it only takes a minute: Sign up Parser Error Message: Ambiguous match found up vote 2 down vote favorite Im running a web application in visual studio 2008.. i got this error when particular page was loaded.. help me to proceed.... Thank u..... Server Error in '/PSS.NET' Application. Parser Error Description: An error occurred during the parsing of a

Ambiguous Match Found Entity Framework

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: <%@ Register TagPrefix="uc1" TagName="CtrlButtonControl" Src="../../WebControls/CtrlButtonControl.ascx" %> <%@ Page language="c#" Codebehind="SPSearchFromToDtStorLocMatTypRank.aspx.cs" AutoEventWireup="false" Inherits="Sdi.Pss.Reports.SP.SPSearchFromToDtStorLocMatTypRank" %> Source File: /PSS.NET/Reports/SP/SPSearchFromToDtStorLocMatTypRank.aspx Line: 1 Version Information: Microsoft .NET Framework Version:2.0.50727.3615; ASP.NET Version:2.0.50727.3614 asp.net share|improve this question edited Aug 19 '10 at 10:27 Nick Craver♦ 430k8410561006 asked Aug 19 '10 at 10:24 John 56282138 add a comment| 5 Answers 5 active oldest votes up vote 2 down vote accepted try these two links - http://forums.asp.net/p/983007/1265347.aspx http://weblogs.asp.net/pjohnson/archive/2006/08/11/Ambiguous-match-found.aspx share|improve this answer answered Aug 19 '10 at 10:29 Sachin Shanbhag 32.3k65888 Really thank u alllllll.... there is two declaration in codebehind file as lblMaterialtype and lblMaterialType.. I just deleted one that im not using.. it works great... thanks a lot.. –John Aug 20 '10 at 9:12 add a comment| up vote 4 down vote I've the same problem and it solved and the solution is in check yo

problem, retracing every change you made, every source control update you performed, attempting to track down the offending bug in code.  Days like javascriptserializer deserialize ambiguous match found yesterday, for example.  I was working on a fairly nondescript ASP.NET web ambiguous match found mvc page, but every time I would attempt to run it I would get the following error: Parser

Activator.createinstance Ambiguous Match Found

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. http://stackoverflow.com/questions/3520809/parser-error-message-ambiguous-match-found Parser Error Message: Ambiguous match found. Source File: /Default.aspx Line: 1 The only thing that is typically on Line 1 of any ASP.NET web page is the Page declaration, which specifies the CodeBehind and Inherits properties, so naturally my first thought was that perhaps the class name for the page conflicted with another class in the same namespace.  But http://www.nicholascloud.com/2010/02/ambiguous-match-really-is-ambiguous-in-asp-net/ this was an erroneous assumption, and after renaming the file several times I decided that was probably not the case. After a few hours of searching, I realized that I had a button on my page declared something like this: and an event on the same page (in CodeBehind) declared like this: public event EventHandler Cancel; As it turns out, when ASP.NET parses a page's controls, it does so in a case insensitive manner, which means that the two "cancel" properties (a button is really a protected property declared in the designer) conflict. This, of course, is completely contradictory, since the code will actually compile (case matters; there should be no name conflict) and only crashes at runtime.  This reeks of FAIL, especially since the whole point of ASP.NET is to make web pages more "object-like". All the more reason to use MVC.