Avatar of LarsNess
LarsNessFlag for Norway asked on

Referencing versions of DLLs

Using .NET 2.0. C#, but I guess the issue applies to VB as well.

I am having trouble understanding how to reference DLLs in other applications that can be updated on the customers system without my knowlodge. Let's say I have a program A that has a reference in source code to version 1.0 of interop.B.dll in application B. I reference version 1.0 of the DLL and includes it with my build to make it available runtime.

This works fine, until the customer updates application B and consequently also updates interop.B.dll to verson 1.1 (and maybe renders my v1.0 uncomaptible).

I'd like to not having to include the DLL with my app and read it from application B's install path, but I can't get it to work. I have tried probing (see atached code snippet) in app.config. No luck.

Can anyone help. What are the best practices in cases like this?
<runtime>
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
  <probing privatePath="c:\program files\application b\"/>
  </assemblyBinding>
</runtime>

Open in new window

.NET Programming

Avatar of undefined
Last Comment
graye

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
graye

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23