Assuming your server is accessible from all the client computers, you can make use of
codebase
element in
app.config
file of your application.
Here[
^] is MSDN page that tells how to specify the assembly location. Following is the example configuration from MSDN (in case the link is dead in future).
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="myAssembly"
publicKeyToken="32ab4ba45e0a69a1"
culture="en-us" />
<codeBase version="2.0.0.0"
href="http://www.litwareinc.com/myAssembly.dll"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
Note that the path to DLL file is a URL and to point it to a server somewhere in your network, path should look something like this:
file://[IP address or name]\folder\filename.dll
Also note that this element works differently for strong named assemblies and private assemblies. Here is an excerpt from MSDN:
Quote:
If the assembly has a strong name, the codebase setting can be anywhere on the local intranet or the Internet. If the assembly is a private assembly, the codebase setting must be a path relative to the application's directory.