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.

Author Greg Duffield

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

14/Jul/2006 09:26 AM

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!!

18/May/2007 17:10 PM

scdealer 101 said:

Read a few comments on this issue, this one actualy helped rather confused. easily found the issue after. Thanks

11/Jul/2007 15:57 PM

Laura Ocampo said:

Thanks! You help me so much!

24/Sep/2007 19:55 PM

DJ said:

Everything is easy when you know where to look....thanks loads!

22/Oct/2007 09:16 AM

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.

25/Oct/2007 13:03 PM

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!

03/Dec/2007 22:35 PM

Magnus said:

Brilliant, this was the "thing" that helped me in the right direction!

05/Dec/2007 10:48 AM

Ryan J. said:

You rule. So simple... gah! Thanks =)

19/Mar/2008 14:18 PM

Ryan J said:

wow... just wow...

19/Mar/2008 14:56 PM

said:

Thanks

24/Jun/2008 12:07 PM

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......

29/Sep/2009 10:28 AM

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

19/May/2010 11:07 AM

Add Comment

Name
Comment
 

Your comment has been received and will be shown once it passes moderation.