About JoderCoder

JoderCoder · ‎Jul 29, 2009

Robert, thanks for the reply, I understand if the silent install is processes by the logged on user, this should work. Do you think this will also assure that it will also run the app as the logged on user when it is installed with Group Plolicy or SMS, etc? I believe that kind tools run the package as NTAuthority or something different that the logged on user.

JoderCoder · ‎Jun 24, 2009

It was a suggestion (from QA) that it would be better not to be able click yes without scrolling to the end. I am not sure if there is a general legal requirement that users should reach to the end before they accept..? I would still like to know the proper way to report bugs and enhancement requests for other issues. Thanks

J_anitha · ‎May 26, 2009

You can change font type using CtrlSetFont().

RobertDickau · ‎May 14, 2009

That registry data is undocumented, so you might consider using a different type of search or the APIs instead; but for information about how those codes are generated, please see for example KB article Q105971.

pwhoriskey1 · ‎Sep 23, 2010

This should be a relatively simple thing to do. Instead it looks like I'm going to have to duplicate the custom action and make sure it runs properly for install, uninstall, rollback, etc. just to hide the window. The precompile option is awesome but I can't use it because the window isn't suppressed.

RobertDickau · ‎Apr 14, 2009

Please see, for example, www.installsite.org > Windows Installer > Tools & Tips > Using the LockPermissions Table on Localized Windows Versions.

JoderCoder · ‎Apr 03, 2009

Found this link http://community.acresso.com/showthread.php?t=185492 So how is the language of the installation determined? Why does the installer display in the language set in Language for non-Unicode programs? Is this documented somewhere? Any input is appreciated guys! thanks!

MichaelU · ‎Apr 01, 2009

Perhaps these variables are different from the usual ones as they don't show up if one runs set in the command prompt. But good point on the invalid characters. Ah well; it was worth a try.

MichaelU · ‎Mar 26, 2009

Required Execution Level applies to manifests which are used in .exe files, so have no bearing for .msi files. There is a setting in General Information > Summary Information Stream "Require Administrative Privileges" which indicates whether the execute sequence needs elevation, but it does not work the same way. It elevates by also running as a system service. One option if you really need to enforce things would be to set a Launch Condition based on the AdminUser property in a project that sets MSIUSEREALADMINDETECTION to 1. In general I would not recommend this; instead relevant custom actions should be set to run deferred in system context.

joshstechnij · ‎Mar 19, 2009

If you don't need to use the states of features from a previous product being upgraded, you can turn off Migrate Feature States. This should allow the new install to use its own states for the features.

MichaelU · ‎Mar 12, 2009

You can add files and registry entries to Filters.xml in the \Support folder - the online help describes this process.

ussraf · ‎Mar 12, 2009

JoderCoder wrote: Is there a handy document that describes how to debug into a C++ dll that is called as a Custom Action? I tried to attach to the msiexec process with Visual Studio 08 with no success. Thanks! Check this: http://msdn.microsoft.com/en-us/library/aa368264(VS.85).aspx

MichaelU · ‎Mar 09, 2009

You can get a little closer to what Chris describes with the Best Practice Components option on the dynamic links, and by adding JAR to the list of file extensions InstallShield should consider as PE files (Tools > Options > File Extensions). If you do that, the dynamic link will create one component per jar file, and use a stable identifier. It won't handle the deleted jar case.

MichaelU · ‎Mar 03, 2009

If you are using a Windows Installer-based project to distribute this file, Windows Installer will use its file-versioning rules, which will treat this file as unversioned (unless you use a companion file, or other table-based mechanisms to override this). In an InstallScript project, the file will also be treated as unversioned, so overwriting will follow the options you select.

MichaelU · ‎Mar 02, 2009

Those characters are available in some locales, but not others, so we tend to avoid them. You may be able to use it in English, but it would fail in Japanese; if this is not a problem for you, go ahead and try it.

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:11 PM

Re: Starting an application at the end of install

Re: RadioButtonGroup in LicenseAgreement Dialog

Re: License Agreement requires to scroll to the end

Re: Retriving the version of the previous install

um me too

Re: Write access for the registry

Re: Localization - Strings not showing in FilesInUse Window

Re: Install logs for serviceability

Re: Required Execution Level for the msi, not only the exe

Re: The states of the features are *sometimes set to Advertise

Re: Ignoring dependency files

Re: Debugging into a Custom Action C++ dll

Re: Dyamic file linking vs Static File Linking

Re: Jar files and versions

Re: Superscript'ed shortcut name

Re: Windows Service install and Recovery Actions

Windows Service install and Recovery Actions

Re: Install windows service

Re: ISDEV : fatal error -6041: Internal build error

Re: ISDEV : fatal error -6041: Internal build error

ISDEV : fatal error -6041: Internal build error

Re: Per user install - ReadytoInstall Dialog - USERNAME resolves incorrectly

Per user install - ReadytoInstall Dialog - USERNAME resolves incorrectly

Re: Always overwrite as a Global Setting

Re: Driver installation prompt