Asp – Ambiguous Reference

asp.net

In my WAP project, every .aspx's code-behind and designer share the same namespace. For example my Main.Master.cs and Main.designer.cs are both in the OurCompany.Web namespace by default.

When I go to another .aspx page and use the following, I get an "Ambiguous reference" error because it can't decide if I'm talking about my code-behind or designer file of that master page

<%@ MasterType  TypeName="OurCompany.Web.Main" %>

but by default this is the way VS creates .aspx pages so should I really care?

Best Answer

The designer files are all marked as "partial" classes so they don't get compiled into their own types.

My guess is that you really do have 2 classes called "OurCompany.Web.Main". A tool like Reflector would let you browser your DLLs so you could tell for sure.

Related Solutions

C# – Ambiguous Reference error during runtime compilation

You can use namespace aliases in your code and use that to differ between them:

using ourOwn=our.own.namespace;

And refer to your Message class as ourOwn.Message. That will avoid the collision.

Asp – User control IDs not Being Recognized in Code-behind after Port to WAP

If they're not recognised in your code behind file, double check that they have been declared in the .designer.cs file. If they are not there, try manually adding them and see if that works correctly.

You might also want to try manually creating a new user control using the File --> New Item option to check that it isn't to do with when you copy and pasted the items in (i.e. they could have the wrong namespace, etc).

Best Answer

Related Solutions

C# – Ambiguous Reference error during runtime compilation

Asp – User control IDs not Being Recognized in Code-behind after Port to WAP

Related Topic