I have an existing VDPROJ that has custom actions to stop and start a service before and after an install. The custom action calls a dll that handles the service state changes. Everything works great as long as the first two digits of AssemblyFileVersion in my service are the same as what is installed. For example, if version 3.5.0 is installed, the custom action will get called when I run the 3.5.1 installer. However, as soon as I try to change the minor version (3.6.0), the custom action no longer gets called and the installer gives a prompt indicating that the exe running the service is in use.
I should note that in my custom actions I also have another action listed under 'install' that calls the exe of the service (which implements InstallerClass). This action doesn't seem to be executing either.
I can't imagine VDPROJ projects would be limited like this. What am I doing wrong? Since this is a legacy product I really don't want to have to migrate to another installer tool.
I'm using Visual Studio 2022.
