Can't change theme image if path includes ".dat"

[Gonnagle]

Short: When trying to set image that has ".dat" in path Advanced Installer crashes as it seems to be trying to read the file. For example if file is at "C:/simple.dataservice/Simple Setup/example-banner.jpg" it crashes telling "Error opening file: "C:/simple.dat"."

Details & repro:

Repro can be found here: https://github.com/Gonnagle/bug-repros/ ... ataservice

Try to change image for the banner for the installer. Go to "User Interface" / "Themes" and select "More options" under "Classic" / "Aero" and then double-click "BannerBitmap" and select a file.



Now as the path includes ".dat" in it, the software seems to be trying to truncate the path there and fails to open the (non-existing) dat-file. Here is an image of the error message. After the error the whole software (Advanced Installer) crashes



The error details can also be found from here: https://github.com/Gonnagle/bug-repros/ ... ice/output

If I change to folder to for example "simple.dadaservice" it starts to work fine. Quickly tested also that .exe and .jpg in foldername worked fine, but did not try any other common file extensions.

[Eusebiu]

Hi,

I tested the scenario and, indeed, I reproduced the problem. This seems to be an Advanced Installer issue. A fix will be available in a future version of Advanced Installer, thank you for bringing it to our attention.

Best regards,
Eusebiu

[Gonnagle]

Hi,

Glad you were able to reproduce the issue and are working to fix this. As in our case this installer is for internal use only, we can postpone adding changing the graphics until the fix is released (if needed could of course also move the images outside of the problematic folder as a workaround).

BR,
Gonnagle

[Eusebiu]

Hi Gonnagle,

Since the developers already work on other fixes and features that will be added in the next release, this fix might be a bit late, so you can implement the workaround in the meantime. Sorry for the inconvenience.

Best regards,
Eusebiu

[Eusebiu]

Hello,

This was fixed in version 16.0 of Advanced Installer released on May 28th, 2019.

Best regards,
Eusebiu