M
markoueis
Our .NET application, let's call it A, needs to load an assembly of
another .NET application, let's call it B. Preferably I would like to
early bind and early load the B assembly. However, in a deployment
scenario, it is possible that B is not installed, in which case, the
dependencies for its assembly won't be there. When I try to load that
assembly (which is copied) regardless, my application crashes saying
that its dependencies cannot be found.
What's the best way to solve this problem? I could late bind the
assembly, but then do I really have to use reflection for each and
every method call I make against this assembly? If this is so, are
there any OO design techniques out there I can use? Is there any way I
can still compile against that assembly?
Are there any good solid articles on this kind of development?
Thanks
Mark
another .NET application, let's call it B. Preferably I would like to
early bind and early load the B assembly. However, in a deployment
scenario, it is possible that B is not installed, in which case, the
dependencies for its assembly won't be there. When I try to load that
assembly (which is copied) regardless, my application crashes saying
that its dependencies cannot be found.
What's the best way to solve this problem? I could late bind the
assembly, but then do I really have to use reflection for each and
every method call I make against this assembly? If this is so, are
there any OO design techniques out there I can use? Is there any way I
can still compile against that assembly?
Are there any good solid articles on this kind of development?
Thanks
Mark