Note: it is possible on an x64 platform to find both the .NET x86 Runtime and the .NET x64 Runtime installed. So I'd recommend that the conditions attached to each version of your custom action be as follows: CallDotNetMethod_x86: ( NET7_X86 ) AND ( NOT NET7_x64 ) CallDotNetMethod_x64: NET7_x64 Othe...
Daniel Thanks for the response and the linked article which makes it clear. May I suggest an enhancement to AI's "Call method from .Net Assembly" wrapper? It could execute the the registry search you've described, decide for me which .Net runtimes are available and use the appropriate one. That's a ...
I have an AI project that calls 11 custom actions on install, and 5 on uninstall. All of these CAs are "Call method from .NET assembly". All assemblies are compiled for "AnyCPU" so can work with whichever .NET Runtime (i.e. 32 or 64bit) is installed on the target computer. However, I am stuck on how...
Hello Catalin - great to be here! The deferred custom action is coded to trap any exceptions and, if this happens, it returns value ERROR_INSTALL_FAILURE (aka 1603) to Windows Installer to tell it that something went wrong. So far, so good. But then ... Windows Installer then pops up a warning messa...
What is the best practice to trigger rollback of an install from within a .Net Custom Action? I have tried using the CA's return value, setting it to 1603 (ERROR_INSTALL_FAILURE). But this triggers a message box to appear saying "Error 2869. The dialog ErrorDlg has the error style bit set, but is no...
