Thank you.
Unfortunately the logging is exactly why I'm having this problem.

Without that I could just package my code in a .exe file and run is as an "Attached Custom Action".
Now, I did find an interesting workaround on the internet. One guy has written a simple native wrapper for .NET .DLL files - exactly for this purpose. It passes the MSI handle along to the .NET code which then imports native functions from msi.dll and can use all the installer features.
But there is a problem with this solution too. In "Attached Custom Action" I can specify only one .DLL file. That has to be the native .DLL. But this native .DLL then needs to load the .NET .DLL file. Is there any way to specify that the installer should extract two .DLL files and the run one of them (afterwards deleting them both)?
FOLLOW US
Get the latest news in Application Packaging