A
Albert Greinöcker
Hi NG,
I have a problem using two dlls in c# via COM which have the same name (and
namespace structure, also the classmodel is identical), they just differ in
their Version, but I want to use them both in my Application. As a
workaround I tried to generate two extra projects for each dll (which should
serve as something like a "wrapper") and set dependencies (these two
projects) in my main project. And now the problem comes up: Visual studio
copies just one of the dlls to the debug-directory of the main application,
and uses just this one (so the functionality of the second dll gets lost).
I know this problem is a bit hard to describe, but I hope someone
understands what's going on and can give me some hints. Maybe one solution
would be to instruct Visual Studio to copy the dlls in different
directories, but I don't know how to do so :-(
Another question which fits into this topic: how can I define some
post-compilation steps (e.g. after compilation, copy the dll to a special
destination folder) in Visual Studio, because this could eventually solve my
problem?
Thanks,
Albert
I have a problem using two dlls in c# via COM which have the same name (and
namespace structure, also the classmodel is identical), they just differ in
their Version, but I want to use them both in my Application. As a
workaround I tried to generate two extra projects for each dll (which should
serve as something like a "wrapper") and set dependencies (these two
projects) in my main project. And now the problem comes up: Visual studio
copies just one of the dlls to the debug-directory of the main application,
and uses just this one (so the functionality of the second dll gets lost).
I know this problem is a bit hard to describe, but I hope someone
understands what's going on and can give me some hints. Maybe one solution
would be to instruct Visual Studio to copy the dlls in different
directories, but I don't know how to do so :-(
Another question which fits into this topic: how can I define some
post-compilation steps (e.g. after compilation, copy the dll to a special
destination folder) in Visual Studio, because this could eventually solve my
problem?
Thanks,
Albert