I have 2 files installed to the same location by 2 different installers (shared files). They are a .Net dll and a .Net exe. The exe is a UI that implements the dll. The exe references the dll.
Both components are marked as shared.
In a situation where both installers are installed on the same system, the shared count would be 2 for both files.
If the dll is updated and thus the version changes, the resulting major upgrade will install the dll.
Except the exe is not upgraded but it needs to be since the .Net exe now binds to a different dll version but its own version did not change.
Aside from the obvious answer of changing the exe version whenever the dll is changed (project lead says no to that), is there any way to force only this file to be updated? I know about companion version files except that using it here would only move the problem around since either file can be updated without the other being as well. I also know about overriding global version rules but that I don't want to do that.
I am also looking into having the exe not bind to the dll but rather to delay load which would work but that may also not fly with the project lead.
Thanks in advance.