GeekZilla
Parser Error Message: Ambiguous match found.
VS 2005 Only.
This can be an annoying error, but it is usually caused by one thing.
If you add an object to your html source such as
<igtxt:WebDateTimeEdit id="dteStartdate" runat="server" ToolTip="The end Date to use for the report." EditModeFormat="dd/MM/yy" Width="60px"></igtxt:WebDateTimeEdit>
By default this will be instatiated in the partial class that is created by Visual Studio 2005. However, there is nothing to stop you specifing the object in the codebehind as well such as
protected Infragistics.WebUI.WebDataInput.WebDateTimeEdit dteStartdate;
And while you are running in Dev this will continue to work, but as soon as you do a release build you will get the Parser Error Message when trying access the page.
A pain but when you know where to start looking it does make it easier to solve the problem.
Greg has too many years experience in developement from VB for DOS all the way through to Windows Workflow and LINQ while covering pretty much every technology in between. A complete MS evangelist he is now Director of the only MS Gold Partner IT services company in Norfolk. Wehere they are producing Web 2 Applications for various sectors, and are currently entering the Haulage industry with their latest product.
Comments
Anonymous
said:
Excellent find. Thanks for sharing
Prashant0268
said:
Thanks a lot for the solution! I was migrating an application to ASP.Net 2.0 and this problem was causing a lots of troubles. I went on to comment all the instances where Controls were again explicitly defined in the Code behind and it worked!!
scdealer 101
said:
Read a few comments on this issue, this one actualy helped rather confused. easily found the issue after. Thanks
Laura Ocampo
said:
Thanks! You help me so much!
DJ
said:
Everything is easy when you know where to look....thanks loads!
mrdeus
said:
Thanks for the solution. I skimmed through other pages describing this, but your post was to the point and solved my problem. All I needed was for someone to say: id="apa" conflicts with member int ApA.
Alex
said:
Great advice! I simply changed ASP.NET version in IIS from 2.0 to 1.1.4322 and my code went working as usual wihtout errors! Thanks!
Magnus
said:
Brilliant, this was the "thing" that helped me in the right direction!
Ryan J.
said:
You rule. So simple... gah! Thanks =)
Ryan J
said:
wow... just wow...
said:
Thanks
Mithun
said:
I got the same error....I tried a lot fo hrs.. finally it got fixed by changing the ID of all controls for which page the error is throwing......
Mohammed Imtiaz
said:
I was facing the same issue while publishing the website ....Thank You very much.for the solution............It worked for me too 
Keep Up the good workl
