1 reply to this topic

[klee777]

Hi I wrote a custom WindowsInstaller DLL which is embedded into the MSI
package, then the admin of ActiveDirectory assigned the MSI via Group policy,
so that the shortcut icon shows up when the user logs in. When the user logs
in and double-clicks the icon, the MSI runs and calls the function in the
DLL. So far so good, but he/she gets the warning dialog:
<Caution>
You are attempting to open a file of type 'Application Extension' (.dll).
These files are used by the operating system and by various programs.
Editing ir modifyibng them could damage your system. If you still want to
open the file, click Open With, otherwise, click Cancel.
<Open With...><Cancel>

After investigation, I found RUNDLL32.EXE prompted this warning dialog.

As a different test, if the user directly browses Active Directory on the
server machine and double-clicks the MSI file, this warning dialog doesn't
show up.

So I am wondering what makes the difference and how to avoid running
RUNDLL32.exe.

Thanks in advance.

[klee777]

My bad...
It was because I set my DLL as a key file. After I cleared the key file, RUNDLL32.EXE didn't display the warning.