Comments for Advanced .NET Debugging

Comment on “Ambiguous match found” in a Web Control – a Possible Bug by Hai

Hai — Thu, 29 Jul 2010 08:55:07 +0000

Thanks Eran,

Your post in 2006 still help me out of the problem when I’m converting my ASP.NET project from 1.1 to 4.0

It seems that MS does not fix this issue ?

Once again, thanks a lot.

Comment on Sys.WebForms.PageRequestManagerParserErrorException by Pushkar

Pushkar — Sun, 20 Jun 2010 06:45:47 +0000

i just added a trigger and it worked fine

Comment on Identifying Deadlocks in Managed Code by Michal

Michal — Thu, 10 Jun 2010 09:23:34 +0000

thanx man, great article, helped to solve my pain in the ass

Comment on Sys.WebForms.PageRequestManagerParserErrorException by Eran Sandler

Eran Sandler — Tue, 01 Jun 2010 15:19:39 +0000

Bhaskar Joardar, you might some httpModule or ISAPI filter install on that machine that causes the output to be changed a little bit, which may cause this issue.

Comment on Sys.WebForms.PageRequestManagerParserErrorException by Bhaskar Joardar

Bhaskar Joardar — Tue, 01 Jun 2010 15:09:38 +0000

Thanks Eran for the post. I have a different kind of problem. I’ve hosted my application in a 2003 server(32 bit) and having this error message.
When I hosted this application in a different 2003 server (64 bit) the error message is not appearing. This arror message is not appearing too when I amrunning the application from development environment. Is there something I need to change in server configuration? Please respond.

Comment on “Ambiguous match found” in a Web Control – a Possible Bug by Ashish

Ashish — Thu, 27 May 2010 08:55:58 +0000

Great post Eran! I could solve my problem within minutes… Otherwise this could have taken a quite enough time to work around. Thanks a lot. Keep the great work up!

Just a note, as in my case the problem was between: LinkbuttonCancel & LinkButtonCancel, and to find this I did not use the reflector or WinDbg. I simply tried with deleting my *.designer.cs file of the page giving this exception and then I right clicked the same page’s aspx file and used the option “Convert to web application” (after deleting designer.cs file you would see this option). This option creates designer file for you and while creating it would notice the difference between the ambiguous fields and an alert would come like:

“Generation of designer file failed: Control LinkbuttonCancel conflicts with field LinkButtonCancel of a different case. Declaring both fields will result in an ASP.NET error.”
And this is what I was looking for….

Comment on “Ambiguous match found” in a Web Control – a Possible Bug by Mohammed Imtiaz

Mohammed Imtiaz — Thu, 20 May 2010 10:14:27 +0000

Hi Eran…

Thx a lot i was facing the same issue and I was trying to resolve that from last 32 hrs.. Now i could resolve it easily … I have used a control name as variable name

Issue diaognised
asp:Label ID=”Projectid” and i had a varibale called “Projectid” in teh code behind….

Comment on Sys.WebForms.PageRequestManagerParserErrorException by Kledi

Kledi — Tue, 11 May 2010 12:31:24 +0000

Thank you very much. this has solved my problem.

Comment on “Ambiguous match found” in a Web Control – a Possible Bug by purushu

purushu — Tue, 04 May 2010 08:43:33 +0000

Thank you for the suggestion what u had given above Eran Sandler.

I got solved my application problem from your Good tips

Thank You

Comment on “Ambiguous match found” in a Web Control – a Possible Bug by Javier Regusci

Javier Regusci — Thu, 25 Mar 2010 15:54:31 +0000

Great post Eran! It really solved the issue.
Thanks!