Issue:
Application uses Library.dll from the same solution and UI.dll from external solution.
Problem is, that UI.dll wants Library.dll too.
With this scheme I faced the issue, when application refused to work with messages about assambly versions.
The first walkaround was to use bindingRedirect element in the configuration. But this solution doesn't woek if you are changing Library.dll and it's version as well.
I stayed with next solution. I turned off assembly signing locally for the UI.dll. If .NET assembly is not signed, it doesn't matter which version you used to build dll. You can use UI.dll with eny higher version of Library.dll.
Application uses Library.dll from the same solution and UI.dll from external solution.
Problem is, that UI.dll wants Library.dll too.
With this scheme I faced the issue, when application refused to work with messages about assambly versions.
The first walkaround was to use bindingRedirect element in the configuration. But this solution doesn't woek if you are changing Library.dll and it's version as well.
I stayed with next solution. I turned off assembly signing locally for the UI.dll. If .NET assembly is not signed, it doesn't matter which version you used to build dll. You can use UI.dll with eny higher version of Library.dll.
