Ambiguous Match Found Error (What causes it)

Posted Friday, November 18, 2005 9:45 AM by C-Dog's .NET Tip of the Day
The issue was found by Microsoft and it is pretty wierd.  Apparently, at one time, a control was named with the wrong case in the location time control (i.e.: blueChipImageLink).  It was since corrected, but the declaration was left in the code behind.  The migration wizard didn't find a matching control in the markup so it left this declaration alone.  For some reason, when you precompile, it has an issue with this.  So basically since I had a control BlueChipImageLink in the markup and blueChipImageLink in the code behind, it caused the Ambiguous Match Found error.

Read the complete post at