Assembly Help - Desperate

[Qiana]

I had a Project (R) in a solution.

Then I had a separate solution that needed the dll for project R.

I copied the dll from the bin directory in project R and put it in the
new project (E) bin folder.

I then added a reference in project E to the project R.

Apparently, there are 2 dlls that are being used by both project R and
E. So, I got this error:
Error: The dependency 'dll1' in project 'project E' cannot be copied to
the run directory because it would conflict with dependency 'dll1'.

So then in project E, I went to add a direct reference to the 2 dlls
that was giving me the problems (Recommended by Microsoft, but with a
warning). This solved the error above. When I added them as reference I
browsed to the bin directory of project E.

Now when I do the build I get this error:

The located assembly's manifest definition with name '' does not match
the assembly reference.

Any suggestions?

 

[csheppard91]

Come to my forum if you need fast help:
http://www.wizardsolutionsusa.com

 

[Lloyd Dupont]

Don't copy the DLL in the dependent solution's bin directory.
Because if you refer a DLL it will copy it from its location to the bin
location before compiling.
If you put it in the destination directory it will try to copy the file to
itself and that would fail because it will try to write a file while reading
it.
Instead create a Top level directory where you copy (after successfull
build) all your DLLs.
And reference it from there.....