In our application we use Firebird as database.
A install-launcher program (a simple win32 program) performs a scripted installation of Firebird, then of the main application, by calling both installers one after the other with command line options.
This always worked with FB2.x - 4.0.5.
The new 5.0.1 installer suddenly misbehaves:
When running the Firebird5.0.1 64bit installer on a fresh Win10 machine, in the same moment when the installer states it's installing MSVC 32-bit runtime libraries, it closes the our install launcher that would install (as a next step) the main application.
It also requires a complete reboot after installation, what it never did before.
The Install launcher is also closed if the FB-installer is launched manually (without parameters) - but only if the install launcher is from a network share and the 32-app was also started from that network share.
The Message "To complete the installation of Firebird, Setup must restart your computer. Would you like to restart now?" shows up in either case.
I tried running the installer with "/NORESTART /Silent /NOGDS32" - then the reboot-question does not show, but the service is also not started. Als it can be started manually, so there seems to be no reason no to do that.
This breaks the automatic installation.
Is there a trick to get that working, or do I have to revert to an older version of Firebird to implement an application installation that runs through in one go?
After some more checking:
If I install the MSVC installer from https://learn.microsoft.com/de-de/cpp/windows/latest-supported-vc-redist?view=msvc-170
If I install the X86 installer, then the launcher application is not closed by the FB installer
If I install the X64 installer, then the FB-installer can launch the FB service after installation.
Both MS installers don't require a system reboot.
Could it be, that the MSVC installation is not done properly by the FB installer?
In our application we use Firebird as database.
A install-launcher program (a simple win32 program) performs a scripted installation of Firebird, then of the main application, by calling both installers one after the other with command line options.
This always worked with FB2.x - 4.0.5.
The new 5.0.1 installer suddenly misbehaves:
When running the Firebird5.0.1 64bit installer on a fresh Win10 machine, in the same moment when the installer states it's installing MSVC 32-bit runtime libraries, it closes the our install launcher that would install (as a next step) the main application.
It also requires a complete reboot after installation, what it never did before.
The Install launcher is also closed if the FB-installer is launched manually (without parameters) - but only if the install launcher is from a network share and the 32-app was also started from that network share.
The Message "To complete the installation of Firebird, Setup must restart your computer. Would you like to restart now?" shows up in either case.
I tried running the installer with "/NORESTART /Silent /NOGDS32" - then the reboot-question does not show, but the service is also not started. Als it can be started manually, so there seems to be no reason no to do that.
This breaks the automatic installation.
Is there a trick to get that working, or do I have to revert to an older version of Firebird to implement an application installation that runs through in one go?
After some more checking:
If I install the MSVC installer from https://learn.microsoft.com/de-de/cpp/windows/latest-supported-vc-redist?view=msvc-170
Both MS installers don't require a system reboot.
Could it be, that the MSVC installation is not done properly by the FB installer?