I am a long time VSPAX OEM customer. I'm currently using 184.108.40.206.
I have always used Visual Studio 2003, which always generated the Interop.VSPortLib.DLL and AxInterop.VSPortLib.DLL files from VSPort.DLL. I also deploy my application using Visual Studio's setup project (MSI generator).
Over the years I've upgraded from VSPAX 3.0 to 4.0 to 6.0 to 6.2.
I'm now using Visual Studio 2008, and in the same manner it generates the Interop assemblies. Interestingly enough, these two DLLS (Interop.VSPortLib.DLL and AxInterop.VSPortLib.DLL) get generated with version 220.127.116.11, even though the VSPort.DLL has a version of 18.104.22.168. (This is done automatically by Visual Studio).
My problem is that when I am performing an upgrade over a previous build of my application, the newly generated versions of the interop dlls are not deployed becaue the installer must think they are identical because the version is the same. All of my own assemblies have version numbers that get incremented, so this isn't a problem for them. Do you have any suggestionsfor how to get the version numbers of these interop assemblies to increment?