Assembly still not picked up after Project -> Add Reference ...

[John Smith]

All,

From the project properties I saw a yellow ! under the reference
section denoting a broken reference. Sure enough when I view the
source code I saw

"The type or namespace name 'FileUtils' could not be found (are you
missing a using directive or an assembly reference?"

After clicking "Add Reference ... -> Browse " and picking out the .dll
that has FileUtil, I still see the same error.

Any suggestions?

Thanks.

 

[John Smith]

All,

From the project properties I saw a yellow !  under the reference
section denoting a broken reference.  Sure enough when I view the
source code I saw

"The type or namespace name 'FileUtils' could not be found (are you
missing a using directive or an assembly reference?"

After clicking "Add Reference ... -> Browse " and picking out the .dll
that has FileUtil, I still see the same error.

Any suggestions?

Thanks.

I am using:
Microsoft Visual Studio 2008
Version 9.0.30729.1 SP
Microsoft .NET Framework
Version 3.5 SP1

Also, how come the .dll does not show up in the GAC either?
GAC: C:\WINNT\assembly

Thanks.

 

[John Smith]

Probably something wrong with the DLL.  But without more details, it's
hard to know for sure.

The same .dll was actually referenced in another project and that
project has no reference errors.
By "same error" I mean I still see the same yellow ! after adding
the .dll from "Add Reference ... "; and see the same error message in
the code.

If there's something wrong with the DLL, I wouldn't expect it to be able
to be registered in the GAC either.

Since the other project successfully referenced that .dll , I would
like to understand why that .dll does not show up in the GAC.

 

[Jeff Johnson]

From the project properties I saw a yellow ! under the reference
section denoting a broken reference. Sure enough when I view the
source code I saw

"The type or namespace name 'FileUtils' could not be found (are you
missing a using directive or an assembly reference?"

After clicking "Add Reference ... -> Browse " and picking out the .dll
that has FileUtil, I still see the same error.

Any suggestions?

Do you have the source code for the assembly that contains FileUtils? In
other words, is this an in-house project or is it a 3rd-party DLL?