One could consider Unicode Inno Setup as the new standard Inno Setup and Non Unicode Inno Setup as an old special Inno Setup for those who want the very smallest size possible.Īlso for Inno Setup 6, there is no Ansi version at all, so if you want to use the latest version of Inno Setup with all
Inno setup studio code#
Key features of Unicode Inno Setup are its ability to display any language on any system regardless of the system code page, and its ability to work with Unicode filenames. The Unicode version does not have these problems, as documented in the Inno Setup installator has wrong text encodingįor the same reason, the Ansi version will not be able to create files with names containing characters, that are not present in the legacy Ansi character set of the target machine. If you have some Pascal Script code, you should be more careful.įor example of problems with the Ansi version, if you run Japanese-only installer built with Ansi version of Inno Setup on English system, you will get: ), you can (and should) switch to the Unicode version straight away. So if your existing installer script does not have any Mostly they are, but there are differences. The reason, why Ansi version of Inno Setup was still available for long time, was that the Pascal Script code of Ansi and Unicode versions are not 100% compatible. Actually there's no Ansi version for the latest Inno Setup 6 anymore. There is no reason to use the Ansi version for new projects. If you are starting new Inno Setup project, always use the Unicode version. Obviously the fact that the Unicode version is not limited to legacy Ansi character set. As I wrote no traces of this problem can be found in the log, it just crashes.
Inno setup studio windows#
Just keep the firewall exception checked and it should crash somewhere near the end of the setup process.īased on the setup log file the tester sent he has Windows version 3. We could not reproduce this issue ourselves, just one of our beta testers using this setup: So there seems to be some more (negative) side effects of the Unicode version.
To be sure it was the change from Ansi to Unicode causing this problem, we send the beta tester another identical build, just compiled with the Ansi version and no crash there. I asked the beta tester to run the setup with "/LOG" parameter and there is no error shown there at all. If this code is executed the setup crashes with Log('Error setting firewall exception: ' + GetExceptionMessage) After the clear answer here that there is not a real reason to stay with the Ansi Inno Setup version, we switched the beta setup of our product to the Unicode version yesterday and did not see any problems in our own tests.īut one of our beta tester reported now today that this version crashes while creating a firewall exception with following code:įirewallObject := CreateOleObject('HNetCfg.FwAuthorizedApplication') įirewallObject.ProcessImageFileName := 'C:\Program Files (x86)\FS-FlightControl\FS-FlightControl.exe' įirewallObject.Name := 'FS-FlightControl' įirewallObject.Scope := NET_FW_SCOPE_ALL įirewallObject.IpVersion := NET_FW_IP_VERSION_ANY įirewallManager := CreateOleObject('HNetCfg.FwMgr') įirewallProfile := į(FirewallObject)
0 kommentar(er)
