>> From what I gather, the OS version should be checked in the >> CustomAction's MSI execution conditions instead of in the CustomAction >> itself. The appropriate information can then be passed in based on that: >> >> https://blogs.msdn.microsoft.com/cjacks/2009/05/06/why-custom-actions- >> get-a-windows-vista-version-lie-on-windows-7/
> The post on this link is true for Windows 7 (May 6, 2009). It's 2018 now and > MSI's property VersionNT got stuck on Windows 8 (602 if I recall correctly). Quite right. I just talked to someone familiar with this here, and, as I understand it, MSI will never offer a way to do this Right on Windows 10. I'm not sure what the general messaging is from Microsoft around MSI, but my personal perception is that it is not moving forward anymore. > I am open to suggestions, how to make a "regular/attestation signed/WHQL" > selection logic in the MSI. MSI packages have up to three driver flavours > packed and only one must be installed: > - x86 MSI has regular+attestation signed > - x64 has regular+attestation+WHQL > - ARM64 will have attestation signed only Fortunately, I *do* have a suggestion here...I think. First, though, let's make sure I'm thinking straight: In your new system, there is an EXE that runs, detects the architecture, unpacks the right MSI, and runs the right MSI, right? *If* I have that right, the EXE could be manifested as Windows-10-aware: Manifest contents: https://docs.microsoft.com/en-us/windows/desktop/SysInfo/targeting-your-application-at-windows-8-1 VS workflow: https://docs.microsoft.com/en-us/cpp/build/how-to-embed-a-manifest-inside-a-c-cpp-application Basically, you write an XML file and pack it in the EXE as a resource. Visual Studio will do this for you if the file is in your VS project source file list. I'm not sure how you'd do this with mingw_w64, but you'd probably invoke the equivalent of mt.exe: https://stackoverflow.com/questions/1423492/how-do-i-add-a-manifest-to-an-executable-using-mt-exe The parent installer could then call GetVersionEx without being lied to and pass it in to your CustomAction DLL through msiexec: https://www.codeproject.com/articles/16767/how-to-pass-command-line-arguments-to-msi-installe Let me know if that doesn't make sense or won't work for what you're doing. Thanks, Jon _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
