Can .NET assemblies reference a COM interop version unspecific

In a .NET assembly I use a third-party COM component (as an API), which is referenced via a COM interop. During delivery, we are not allowed to deliver this COM interop. If exactly the same version of the third-party COM component is installed on the target system, then this can be called/loaded. If an older/newer version of the third-party COM component is installed, then the COM interop must be next to our assembly so that the COM component can be loaded.

If our assembly is built against the same COM interop version as on the target system, then the COM component can be loaded without the COM interop being placed next to it. If the version is different, then the COM interop must be placed next to our assembly.

Is there a way to turn off this version specificity during the build process?

It does not work with the setting "Specific Version = False" on the COM interop reference in Visual Studio.

If we could switch off this version specificity, then we could take the COM interops on the target system with a different version and place it next to our assembly.