• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

The referenced component could not be found (C#, VS2005-SP1)

S

StefanM

#1
Hi,

every now and then I get this warning on a simple C# project which
just contains one .cs-file for some base classes. The only referenced
DLL is for a typed dataset. The project of the typed dataset is also
included in the solution.

When I try to rebuild my project I get this warning and the referenced
DLL gets marked with an exclamation mark in the solution explorer. If
I click on the reference the mark disappears. I already tried to
delete then add the refenrence again. But still "rebuild" brings up
the warning.

The property "Specific version" is set to "false". The DLL exists in
the given path. It makes no difference wether "Copy Local" is set to
true or false. Normaly I use "true".

Can somebody tell me what I have to do to get rid og this warning?

TIA,
Stefan
 

My Computer

P

Pavel Minaev

#2
"StefanM" <stefan.spam@xxxxxx> wrote in message
news:c91202f2-d3d9-4e23-a04a-1b89c26f6c01@xxxxxx

> Hi,
>
> every now and then I get this warning on a simple C# project which
> just contains one .cs-file for some base classes. The only referenced
> DLL is for a typed dataset. The project of the typed dataset is also
> included in the solution.
>
> When I try to rebuild my project I get this warning and the referenced
> DLL gets marked with an exclamation mark in the solution explorer. If
> I click on the reference the mark disappears. I already tried to
> delete then add the refenrence again. But still "rebuild" brings up
> the warning.
It sounds like you have two projects in your solution, and you've referenced
a DLL built by one project from another project directly as a file (i.e.,
you added a file reference, not a project reference).

In this case, I wonder if what actually happens is that you rebuild the
entire solution (and not just the second project). When it builds the first
project, it deletes the .dll before rebuilding it - perhaps at that moment
VS itself detects it, and displays that warning? Of course, by the time you
click on it, the first project has finished building, and the DLL is already
there...
 

My Computer

Users Who Are Viewing This Thread (Users: 1, Guests: 0)