http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660@Markus, It did, that is when we started to do a line by line change. I didn't even consider that line, forgot that I even had such a control http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment9http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment9Tue, 10 Jul 2007 18:12:01 GMT****@robert : I used to prefix the controls with the ControlType like you suggest, but then its a mess when you change they type of control you're using. For instance, going from a Literal to a Label, or DropDownList to RadioButton, etc... I've moved to a convention of prefixing the control names with ux, for User eXperience. This approach still results in nice groupings in IntelliSense while making the controls a bit more generic from the naming perspective. http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment8http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment8Tue, 10 Jul 2007 14:14:43 GMTIt's an error with the asp.net compiler. While C# is case sensitive, this compiler seems to not be. You will also get those errors if you try to compile the virtual directory using the aspnet_compiler.exe command line tool. The error happens when it's compiling the ASPX file and the CS file into a single unit. http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment7http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment7Tue, 10 Jul 2007 11:46:02 GMTDidn't it help to diff against the latest working revision. That's what I do even before I restart VS ;-) http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment6http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment6Tue, 10 Jul 2007 06:44:10 GMTI had read about this issue a while back and suffix all controls with a '1' like the designer creates to avoid this stuff and so I can reflect on view interfaces with a simple naming convention. http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment5http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment5Tue, 10 Jul 2007 06:11:44 GMTNot really, it was an error that occured only on runtime, no issue when compiling. http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment4http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment4Tue, 10 Jul 2007 05:59:34 GMTFor me it helps to use prefixes. Txt, lbl, ddl, dg, dl etc. Mostly to group control for entillsense. Means that you collect the data from form, just start to type "txt"... and you see which text inputs need your care. http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment3http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment3Tue, 10 Jul 2007 02:42:42 GMTAhh the joy, we now use variables that refelct the control type as well as the content to stop this kind of issue - e.g. ProductsTextBox. http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment2http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment2Tue, 10 Jul 2007 00:33:01 GMTso Resharper didn't help in that case? http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment1http://ayende.com/2627/total-frustration-ambiguous-match-exception-with-webforms#comment1Mon, 09 Jul 2007 22:29:45 GMT