Comments on: Custom installer without warning dialog… (TrustedInstaller.exe) http://blog.kalmbach-software.de/2009/06/09/custom-installer-without-warning-dialog-trustedinstallerexe/ Infos about Windows development and dotNET Framework Thu, 29 Jul 2010 11:53:41 +0000 http://wordpress.org/?v=2.3.3 By: jkalmbach http://blog.kalmbach-software.de/2009/06/09/custom-installer-without-warning-dialog-trustedinstallerexe/#comment-332 jkalmbach Wed, 10 Jun 2009 05:34:52 +0000 http://blog.kalmbach-software.de/2009/06/09/custom-installer-without-warning-dialog-trustedinstallerexe/#comment-332 Yes; there are other build-in diagnostics of setup-tools... but I do not know the details... Also be aware, that there is a shim called "SpecificNonInstaller" which looks like it might overcome this "detection"... But I am not sure... But this blog entry was also to prevent users to name their products anything with *instal*... this will force an dialog... For "setup/install/update" there are also several entries in the shim database: [I changed my blog entry, to reflect this info...] Yes; there are other build-in diagnostics of setup-tools… but I do not know the details…
Also be aware, that there is a shim called “SpecificNonInstaller” which looks like it might overcome this “detection”… But I am not sure…

But this blog entry was also to prevent users to name their products anything with *instal*… this will force an dialog…

For “setup/install/update” there are also several entries in the shim database:
[I changed my blog entry, to reflect this info…]

]]> By: Koro http://blog.kalmbach-software.de/2009/06/09/custom-installer-without-warning-dialog-trustedinstallerexe/#comment-330 Koro Tue, 09 Jun 2009 21:10:25 +0000 http://blog.kalmbach-software.de/2009/06/09/custom-installer-without-warning-dialog-trustedinstallerexe/#comment-330 What about "setup.exe"? I always thought Vista dug into installer EXE files to detect NSIS or something - it never failed to detect it no matter the name of the installer. What about “setup.exe”?

I always thought Vista dug into installer EXE files to detect NSIS or something - it never failed to detect it no matter the name of the installer.

]]>