Hello,
Daniel wrote:The service "Error Control" option doesn't affect the setup package installation behavior. It only affect the system's behavior when the service fails to start.
Yes you are right. But as I told you, only compiling the same merge-module project with the new AI has caused the merge-module to act different.
But I think I found out what is different. It has directly nothing to do with the "Error Control". The problem is, that the old version of my merge-module (AI v.8.6 I think) actually installs at least the registry entries of the service, and then it is not able to start it. The new compiled merge-module doesn't. It fails already by trying to install it (no registry keys). So, the installation procedure works different among AI versions.
A bit of clarification: As I wrote, this is not a big problem (at less not for me); I was not able to configure the service correctly, so it is correct that the service is not installed (or installed but not started), since in both cases it fails due to the missing configuration. I just wanted to point this out because the same project regenerates different behaviors when compiled with different versions. You guys have created a very good, powerfull, easy to use, installation tool, and I just want to help to maintaining it so.
Daniel wrote:However, in order to have a better view about your scenario, can you try to isolate in two samples (one created using an older version and one created using our latest version) the behavior you are describing and send them us to support at advancedinstaller dot com so we can test and investigate this?
I have the two projects, but I have overwritten the merge-modules. I will try to generate them again with an old AI (I have only the v.11 installed at this moment). If the behavior appears I will send you the files to your support address.
Thanks
Keneth.
FOLLOW US
Get the latest news in Application Packaging