Reference a .NET dll that is on another network computer.

[chu2ch]

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

 

[Michel Posseth [MCP]]

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

 

[Mr. Arnold]

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.

All that's going to happen is that the DLL is going to be copied to the
machine that needs the reference to the DLL . The DLL going to be copied to
wherever the exe is located on the machine that has reference to the DLL.
The VS IDE is going to do it by itself and make the copy.

 

[Phill W.]

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).

No problem, /so long as/ you have Code Access Security Policies in place
"trusting" the network file share where the dll resides - I'm guessing
you already have, if the "compatible application" already runs from there).

How can I add that reference to my client project on my development
machine that will consume that dll.

Just add a reference and browse to the Dll. The IDE will take a local
copy of it.

When the application /runs/, the Dll will be located by the Framework as
and when a client application needs something from it. The easiest way
is to leave it in the same directory as the client application.

HTH,
Phill W.

 

[chu2ch]

Well ,,,

Normally this is not a problem

I have created a .net 2.0 dll written in vb.net


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


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

Hello and thanks for your responses.

I believe that reflection is what i will need, because "the release
project should refernce a remote dll". However, i am new to
reflection, and i am wondering if anyone can point me in the direction
of any good learning resources. What i am really interested in is
subscribing to the events that are defined within the remote dll.

Your help is appreciated.

TIA.

Chris