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 ...
I need to run some .NET code of my own creation sometime during the installation. I would also like my code to be able to log any error messages together with the rest of installer messages in the LOG file. After my code has executed, there is no point in keeping it on the computer, so ...
FOLLOW US
Get the latest news in Application Packaging