All geek questions in one place

Does AssemblyBinding in a .NET application work with the old version if the new version is not available?

I have specified assembly binding for a newer version of the assembly used in my application and it works fine.

However, on one of my client machines there is no new version of this assembly, but the old one is present instead. When I try to run the application, it says that it cannot find the new version, which is normal, I think. The question is, how can I say that the .NET platform uses the previous version if the new version is not available?

The goal is to have a unique configuration file that automatically works depending on the version of the assembly installed on any client machine. I want to have a unique configuration file that works as follows:

  • if the referenced assembly has version 1, than use this version 1.
  • if the referenced assembly has version 2, than use this version 2.
  • ... etc.

I am trying to avoid changing assembly information at runtime, depending on the installed version of this reference assembly.

Any ideas? Thank.

+3
source share
1 answer

You will have to load the assembly at runtime, using Assembly.Loador something in that direction. .NET assembly redirection does not support if statements and backups and the like.

0
source

Source: https://habr.com/ru/post/1727871/

More articles:


All Articles