Problem: DLL Made in VB.NET Is Not Referenceable

12 Sep 2006 7:14 PM

Phil Galey

I have a DLL that I created in VB.NET. I haven't had a problem referencing
it in the past, but now I suddenly do. I re-build it and then reference it
from my application, but when I type Imports to import it, the intellisense
doesn not include it. If I type the name of the DLL, it complains that the
namespace for the type "<name of DLL>" cannot be found.

I've restarted my system, but that didn't help. What might be causing my
DLL to not be referenceable? Thanks.

13 Sep 2006 2:45 AM

David Hogue

Phil Galey wrote:

> I have a DLL that I created in VB.NET. I haven't had a problem referencing
> it in the past, but now I suddenly do. I re-build it and then reference it
> from my application, but when I type Imports to import it, the intellisense
> doesn not include it. If I type the name of the DLL, it complains that the
> namespace for the type "<name of DLL>" cannot be found.
>
> I've restarted my system, but that didn't help. What might be causing my
> DLL to not be referenceable? Thanks.
>
>

Hard to say what the problem could be. Are you referencing it as
another project in the same solution or as a file? Is it in the GAC.
Did you build it in 2.0 and reference it from a 1.1 project? Just
throwing some ideas out there.

One thing you might try is removing the reference and re-adding it.

--
David Hogue

13 Sep 2006 7:28 AM

Damien

Phil Galey wrote:

> I have a DLL that I created in VB.NET. I haven't had a problem referencing
> it in the past, but now I suddenly do. I re-build it and then reference it
> from my application, but when I type Imports to import it, the intellisense
> doesn not include it. If I type the name of the DLL, it complains that the
> namespace for the type "<name of DLL>" cannot be found.
>
> I've restarted my system, but that didn't help. What might be causing my
> DLL to not be referenceable? Thanks.

Have you changed the Root Namespace property of the project to
something completely unexpected? If you're in Visual Studio, it might
be worth bringing up the object browser (Ctrl-Alt-J), and expanding the
assembly to see what namespaces it's exposing.

Damien