Our default used to be INSTALLLEVEL 3, but Microsoft default is 1. By
overriding Microsoft default in Property table, we override the
INSTALLLEVEL user might have specified on the command line.
Since our installations no longer use "Minimal/Typical/Full", we may
squash "Minimal" and "Typical" into Minimal.
Signed-off-by: Simon Rozman <simon@rozman.si>
This allows us to use `git clean` without risking to loose keypair,
since it is typically .gitignored and not included in the Git
repository.
Signed-off-by: Simon Rozman <simon@rozman.si>
NMake inline files are always created using ACP. The "1252" in the .idtx
header has no effect on this. However, we must encode the .idt files
using correct charset/codepage regardless the ACP being used on the
building machine.
Signed-off-by: Simon Rozman <simon@rozman.si>
MSVC needs them to use correct charset when Language for non-Unicode
programs is set to Windows-1252 or anything different than UTF-8.
Signed-off-by: Simon Rozman <simon@rozman.si>
Updater will treat all hashes as SHA-256 when checking for updates in
the new catalog - the future releases.
While we keep hashing and signing the old catalog file using SHA-1 - the
past releases.
Signed-off-by: Simon Rozman <simon@rozman.si>
This reverts commit 4cd1196d14.
Due to Active Setup StubPath bug in already deployed MSI packages we can
fix automatically using minor update only, we cannot change the
component GUIDs just yet.
Signed-off-by: Simon Rozman <simon@rozman.si>
This reverts commit caff629534.
Due to Active Setup StubPath bug in already deployed MSI packages we can
fix automatically using minor update only, we cannot change the
component GUIDs just yet.
Signed-off-by: Simon Rozman <simon@rozman.si>
The m_ok variable was not initialized, and set to true in case of
successful initialization - it depended on pure luck.
Since debug versions usually initialize stack and heap allocated memory
(to 0xCD or something like that), this explains why update check was
failing silently and randomly in release versions.
Signed-off-by: Simon Rozman <simon@rozman.si>
Rather than addressing numerous code analysis warnings Microsoft Visual
Studio 2019 reports for wxWidgets upstream, disable code analysis for
the time being. But only for the wxWidgets part. We still want to know
what the code analysis has to say about our code.
Signed-off-by: Simon Rozman <simon@rozman.si>
