Hello, thanks for looking at my question.
Our installer has a custom action calling a function in one of our DLLs (when a prior version of the product is installed).
Our product is x64 (mostly).
Now, running the installer on an ARM64 system, the custom action fails with an error that a DLL required could not be run.
Could you, please, explain why that happens? I understand that AI provides a wrapper to call functions in standard DLLs. I also understand that AI is x64-based. So, why does it fail to load our x64 DLL and call a function in it?
Does it rely on some system DLL to make a call and that DLL is, of course, ARM64 and that's why it fails?
Can you suggest a workaround? My current approach is to use PowerShell with crazy method definitions and twists and turns to ensure a proper architecture PowerShell is used.
Thanks!