How to reference managed dlls from another drive than that of the executable

Question

0.00/5 (No votes)

See more:

Dear Professionals,

My project is a C# windows application to which a dll is added as reference.

When deployed the executable goes to the c:\ of the local machine at the client place.

If I have to make changes in the dll, it will not be appropriate to copy the updated dll to the local machine. I have to copy somewhere in the server and have my project refer it from there.

In Short: I want to keep the executable at the workstation and the dlls in the server and set the path somewhere for my project to refer.

What I have tried :

1. In the dll properties made 'Copy Local' as false and changed the path to the location I want to.
2. Tried the <runtime><probing> element in the App.Config

Please suggest a right method. Thanks in advance.

Posted 5-Jan-16 21:24pm

Priya-Kiko

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

*dan!sh* · Accepted Answer · 2016-01-05T21:45:00

Solution 1

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

XML

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

Posted 5-Jan-16 21:45pm

dan!sh

Updated 5-Jan-16 23:55pm

v3

Comments

Priya-Kiko 6-Jan-16 3:57am

Thanks for your quick response.

If I have have more than 1 dll then should there be an entry for each and every dll and is the publicKeyToken mandatory. Please advise.

dan!sh 6-Jan-16 4:04am

Yes you will need assemblyidentity node for all the references you have. You can skip public token AFAIK.

Priya-Kiko 6-Jan-16 4:16am

Thank you, I will try it and get back.

Priya-Kiko 6-Jan-16 4:59am

I tried this code in App.Config for my 2 dlls. acc.dll and adm.dll. It doesn't seem to work. Have I got the syntax right. Please advise. Thanks. (Not able to submit with tags here.)

runtime
assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"
dependentAssembly

assemblyIdentity name="acc"
codeBase href="h:\mydlls\acc.dll"

assemblyIdentity name="adm"
codeBase href="h:\mydlls\adm.dll"

dependentAssembly
assemblyBinding
runtime

dan!sh 6-Jan-16 5:55am

Check the updated response.

Priya-Kiko 6-Jan-16 23:49pm

Thank you professional. I have changed my app.config as you have told. The code after changing is as below.

runtime
assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"
dependentAssembly
assemblyIdentity name="acc"
codeBase href="file://192.168.0.1\soft$\mydlls\acc.dll"

assemblyIdentity name="adm"
codeBase href="file://192.168.0.1\soft$\mydlls\adm.dll"
dependentAssembly
assemblyBinding
runtime

Here 192.168.0.1 is my server's IP and soft$ is a volume share name and mydlls is a directory in that location. I can view the directory listing when I click on that link.

In my project for the dlls I have given 'Copy Local' as false and generated the exe. Don't know if I'm on the right track. The exe is not finding the dlls from that location. Please help. Thanks in advance.

Priya-Kiko 7-Jan-16 4:45am

Thanks a lot. Was able to get it resolved through your directions. Thanks again.