How to work with Assembly Dependencies?

[alexander.glass]

I have a strange problem and I cant fix it because I don't understand
how assembly dependencies work. I created a project "project 1" that
used two assemblies: "assembly xyz" and "assembly 123". I create a new
project and add "assembly xyz" from the "project 1" folder. Now I am
told that

The required assembly 'Assembly 123' could not be found.

If I try and create new projects now and move "assembly xyz" to any
other folder on the machine this problem persists. I have tried
digging through the registry but cant find out why dotnet thinks there
is some relationship betweeen assembly 123 and xyz.

Maybe someone can shed some light on this.
Thanks
alex

 

[Michael Nemtsev]

Hello (e-mail address removed),

Try to move you "assembly xyz" to the debug folder of the new project.
Did the problem persist?

I have a strange problem and I cant fix it because I don't understand
how assembly dependencies work. I created a project "project 1" that
used two assemblies: "assembly xyz" and "assembly 123". I create a
new project and add "assembly xyz" from the "project 1" folder. Now I
am told that

The required assembly 'Assembly 123' could not be found.

If I try and create new projects now and move "assembly xyz" to any
other folder on the machine this problem persists. I have tried
digging through the registry but cant find out why dotnet thinks there
is some relationship betweeen assembly 123 and xyz.

Maybe someone can shed some light on this.
Thanks
alex

---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch

 

[Rob R. Ainscough]

Don't move anything under VS 2005, you'll regret it.

You need to do make sure:
1. No circular project dependancies (i.e. project XYZ requires project 123
and project 123 requires project XYZ) - break them out to more logical
classes
2. When adding references, add reference as .NET Project and point to the
vbproj (project file) and not the DLL.

Rob.