I have created a custom action to run a c# dll. I have one function working so I understand the concept of how to make it work. I added a new function to open a form with a FolderBrowserDialog. I have tested the dll independent of the installer and the dialog works perfectly.
But when I run it from the custom action in the installer, when the form loads and the user clicks the button to open the FolderBrowserDialog, the form hangs. The dialog never opens. There is a windows application log that talks about a security for the user. I am logged into the Windows Server 2012 machine as Administrator. I have tried running the installer as administrator. It only hangs when launched from the installer. The option to run under the localsystem account with full privileges is grayed out in professional. Is this the possible issue, since the dll works fine when not run from the installer?
FOLLOW US
Get the latest news in Application Packaging