DLL Hell in vb.net

[G B]

I am having one of those days!! I hope somebody can help

I have a solution with many projects and using project references

MyCompany.Solution
MyCompany.Utilities.dll
Mycompany.WinForms.dll (this one Project ref the above)
MyCompany.WinAppUI

many of my projects reference the Utitilies.dlls

Now when in MyCompany.WInAPPUI i add a control that belongs
to the "MyWinforms.dll"
it first complains ".net assembly "MycompanyUtilities.dll" could not be
found.
2nd time round it says that "Unable to write to output file because
process is in use by another ...."

Now Should vs.net handle all that with project references.
I have checked my copylocal and is set to true.

I hack that i have found is that if i had manually the utilities.dll it
works.

can somebody clarify how things should be done?

it is driving me mad.
Article q313512 was short and didnt solve my problem.

anybody PLEASSSEEEEEEEEEEEEE




Thanks
vbnetuk

 

[CJ Taylor]

Might want to check what versions of your utilities class your projects are
referencing. Could be a mixup where one is referencing an older version in
a different directory.

That's my best guess at least.

When doing something like this, get it pretty solid and keep it in a
directory specifically for releases of that dll. That way, everything stays
uniform.

 

[G B]

Thanks for your reply.

The all issue with project reference is that you dont have to worry
about "old,new " dlls.

Vs.net should do it.

If i have a control that reference a dll via project referencing.When
dropping the control on the form should it create all the refs necessary
automatically?

if so what am i doing wrong??

thanks


vbnetuk