Thread: ambiguous in the namespace 'ASP'

I created a thread about this issue before but it's re-appeared and was wondering if anyone had any ideas how to fix it permanently. I thought I'd start a new thread as I've narrowed down the problem to a small area.

I have a few custom controls in my pages and every so often, normally after uploading a change to a BOL, DAL or BLL file the site will throw an exception saying so and so name is ambiguous in the namespace 'ASP'.

It always relates to either these custom controls or my master page.

The only way I've found to solve this issue is to include a ClassName in the Control declaration and call it some random name:

Code:

<@ Control Language="VB" ClassName="nvconcvr" codefile="client_tabs.ascx" inherits="client_tabs" %>

So, if I upload a changed file, I'd get an error saying nvconcvr is ambiguous in the namespace 'ASP'. It doesn't happen everytime a changed file is uploaded, just sometimes.

When it happens I have to change the random class name in my custom controls and master page to something else. I've also tried it without classnames, but then it just throws an exception on the .NET generated names.

I know it has something to do with the re-compiling when an App_Code file is uploaded, but wondered if there's anything I can do to resolve this permanently?

I've googled loads about it, but no-one seems to have a solution, other than changing the names, which becomes a bit tedious when you're making changes, re-uploading, testing and then get this exception, so you have to change 3 files and re-upload those.

Any ideas?

Sorry J. Maybe I wasn't explaining this right.

I have a couple of custom controls that are included in some pages. The code I posted was the directive of one of the controls.

If I include the ClassName attribute in the directive with some random letters, it works until it throws the ambiguous exception again, normally when I upload a changed DAL, BLL or BOL file. If I then change the ClassName for some different random letters, it works again.

What I meant with regards to the master page was that once I get this error I get it for all the custom controls on the specifc page and the master page, so I have to change the random letters in the ClassName attribute of the directive for the controls and my Master page.

Then it works again.

Does that make more sense? What I was wondering was how to stop this error permanently.

Yeah...IIS on a hosted server.

Would it be worth contacting my host and seeing if they can change anything?