parser error message: Ambiguous match found

[Francois]

This is from a Dot Net 1.1 project converted to Dot Net 2.0.

In 1.1, all was fine without any problem.

In 2.0, on the developement machine all seems more or less OK.

In release mode on the test machine, I have this error. at Line 1.
Which is very explanative.

What should I look for ?

Thanks.
François.

 

[Kevin Spencer]

Look for class name references that omit namespaces. It sounds like you have
a conflict of 2 class name references (without explicit namespace) that
could be in more than one namespace.

--
HTH,

Kevin Spencer
Microsoft MVP

Printing Components, Email Components,
FTP Client Classes, Enhanced Data Controls, much more.
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net

 

[Francois]

Seems that it was a variable name problem.
In the ASPX page, I had MyZone ID.
In the CS code, I used myZone variable.

I fear this was the origin of the problem.

I thing I did not still understand is that I could run the pages on the
development computer. Even if I was not under debugging. (and of course no
build error).

But on a computer without dev tools, I had the ambiguous error.

Thanks.

 

[Hans Kesting]

Look for class name references that omit namespaces. It sounds like

you have a conflict of 2 class name references (without explicit
namespace) that could be in more than one namespace.

Kevin Spencer

And some candidates for this are 'Menu' and 'Login', both of which now exist
in System.Web.UI.WebControls. (I had a compile-time issue with both)

Strange that the error is only on the test machine?

Hans Kesting