Ambiiguous in Namespace PROBLEM...

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

jeff - 20 Apr 2007 15:00 GMT

Problem...

I have a project ... winform

During Compilation ... I 'accidently' tried to drop a control onto a form
during compilation.

Error Window Appeared ... saying I can not do that while the project is
compiling.

No problem... at least I thought.

Now, all my custom user objects (~100) all cause the following errors...

<object> is ambiguous in the namespace <namespace>

This happened right after the I did the above action. Now I can not recover
my application from this ... before I do something drastic ... THROW MY
COMPUTER OUT THE WINDOW ... are there any files that may have been corrupted
due to the error above, and if so, where are they and how to I fix them,
delete them ... whatever I need to do.

Like I said, this project was working fine...I added a new custom control to
my toolbox ... selected 'Rebuild' project ... before this ended, in the
toolbox, I clicked on and dragged the new custom object to a new form. This
cause the IDE to crash on the compile ... not stop and kick me out of VS,
but just a message box saying you can not do that while I am compiling.
After that, I tried to recompile / rebuild ... and now ALL my objects (forms
and all) give me this <object> is ambiguous in the namespace <namespace>
error.

Any help would be greatly appreciated.

Thanks
JEff.

Reply to this Message

jeff - 20 Apr 2007 15:35 GMT

Well, after comparing files (agianst yesterday's back) ... here is what I
figured out...

when the compile process crashed, it all the following to the Visual Basic
Project File for myEMS project...

<Reference Include="myEMS, Version=1.0.0.0, Culture=neutral,
processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>obj\Release\myEMS.exe</HintPath>
</Reference>

Basically, reference back to itself. Making two references to all the items
in the project. The one because it is the project (implicit) and the second
one this file states (explicit)... Make sense???

Not sure if this make sense to you, but by removing these lines from the
project file, I was able to remove the ambiguous errors and get a stable
build once again.

Now, when I attempted to reproduce this error, I did the following...

- started the compiling ...
- dragged and dropped control to a form
- caused compilation process to fail.
- this broke my applicaiton with the ambiguous error
- rebuilding / cleaning / building ... did nothing to resolve this.
- I closed VS IDE
- went to project BIN and OBJ folder
- remove ALL files from the DEBUG and RELEASE folders
- reopened VS IDE ...
- select solution
- rebuild solution.
worked...

So, I am not sure how these lines got in the file...I am not sure what
happens....but I know if it happens again, I need to ...

close vs ide ...
delete files in the project's bin and obj folders
reopen sc ide
build the solution.

done.

if this does not work, i check the project file for Reference Include
section that explicitly references the same project.

Jeff

> Problem...
>
[quoted text clipped - 31 lines]
> Thanks
> JEff.

Reply to this Message

Rate this thread:

Ambiiguous in Namespace PROBLEM...

Free Magazines