Well ,,,
Normally this is not a problem
I have created a .net 2.0 dll written in vb.net
that needs to reside in a folder on a networked computer ( for
compatibility with another program). How can I add that reference to
my client project on my development machine that will consume that
dll.
In the company i work we have a network folder were all programmers release
there reusable modules that may be used by other programmers in our company
and setting the refernce to the remote dll is no problem , when we compile
the proggy all dll`s are automaticly copied to the bin folder of our project
( this is standard behavior of VS.Net )
However this line
>please keep in mind that the computer name or path may change.
Is confusing me ,do do you mean by that that after the proggy is compiled
it needs to reference the assembly on a remote location ?
cause as i said VS.Net copies the Dll local to the bin directory when
compiling the project as all .Net proggys are standard XCopy deployable
If you really mean that the release project should refernce a remote dll
from who te location might change , well in that case you could use
reflection however when reflecting to the target the proggy must know 2
things
1. the interface it is reflecting to ( typicly provided by a interface
assembly, or a skeleton copy of the target )
2. the location ( path ) of the actuall assembly ( i read this with one of
my projects from a database )
well HTH
Michel
<ch****@gmail.comschreef in bericht
news:11*********************@x35g2000prf.googlegro ups.com...
Good Afternoon Folks,
Im kinda in a pickle. I have created a .net 2.0 dll written in vb.net
that needs to reside in a folder on a networked computer ( for
compatibility with another program). How can I add that reference to
my client project on my development machine that will consume that
dll. please keep in mind that the computer name or path may change.
Thanks in advance.
Chris