About eladef

TsungH · ‎Feb 27, 2010

If you have not, you will want to look at Create MSI Logs under General Information View Settings.

joebatngc · ‎Dec 10, 2013

Has this anomaly ever been solved? I am currently seeing this behavior with InstallShield 2012 Professional on a target Windows XP Pro SP2 clean machine (VM) with only .NET 2.0 SP2 installed. My Basic MSI project selects the Microsoft .NET Framework 3.5 SP1 redistributable for installation. This redistributable has a default set of prerequisites that I have not edited. In addition, as far as conditional installation, the "Install before feature selection" option is checked (this was default selection). When I run the setup.exe on a Windows XP Pro SP2 machine with no other version of .NET installed, the engine detects that the prerequisite conditions have been satisfied, and I get prompted with the following: However, when I run the setup.exe on a Windows XP Pro SP2 machine with .NET 2.0 SP2 installed, I am not presented with this dialog, and the installer proceeds to the InstallShield wizard. But, this only happens the first time I invoke setup.exe. On subsequent invocations, I am prompted to install .NET Framework 3.5 SP1, as expected.

eladef · ‎Jun 16, 2010

Is there a workarounf for it ?

eladef · ‎Mar 19, 2009

Ooooops 😮 Don't know how did I missed that.

eladef · ‎Aug 18, 2008

Any suggestions ? I also tried with this command line /q /norestart but problem was not solved.

hidenori · ‎Apr 01, 2008

The InstallShield Self-Registration method in InstallShield 2008 supports 64-bit self-registration. Here is the description from the release notes: Support for 64-Bit Self-Registration of COM Servers (Basic MSI Projects) InstallShield now includes support for 64-bit self-registration of COM servers in Basic MSI projects. If you mark a component as 64 bit and then add a file to that component, you can select the file's Self Register check box to enable 64-bit self-registration of that file during installation. In addition, InstallShield also supports 64-bit self-registration of dynamically linked COM servers.

arsirantala · ‎Feb 26, 2008

No setup wizard but a major upgrade? I don't think its possible.. correct me if I'm wrong. Alternatively you could create a patch instead? it'd modify the existing installation.

g_noyer · ‎Feb 20, 2008

I do not think there are automatic way to do that. In fact it seems that you have removed files from one version to another one. In this case, you need to populate manually the RemoveFile and RemoveRegistry table.

kdelloyd · ‎Feb 11, 2008

Take a look at this thread - it's not using ProductVersion, but it should help: Making INSTALLDIR relate to ProductName property Hope it helps! 🙂

DebbieL · ‎Dec 17, 2007

Perhaps you could set a feature condition on the custom action—something like &MyFeature=3. With this condition, if MyFeature is installed locally, then the custom action is run. For more information on how to write conditions, see "Conditional Statement Syntax" in the help. Would that meet your requirement? Debbie Landers Macrovision Corporation

klacounte · ‎Dec 04, 2007

I think you'll need to write a CA that gets the parent directory of INSTALLDIR then use MsiSetTargetPath to modify the directory associated with those components.

joshstechnij · ‎Dec 04, 2007

I'm able to successfully enter a UNC path in the "Folder path" field on the InstallChangeFolder dialog. After clicking OK, INSTALLDIR is updated to the UNC path I had entered. Is there some other behavior or errors you are seeing when trying this?

arsirantala · ‎Feb 26, 2008

eladef wrote: Our solution ( if we can call it so ) was to register them with regasm.exe by code. What about uninstallation? Did you guys have CA to uninstall the registeration of the component(s)? How have you resolved the scenario that user uninstalls the software from the computer. If I understood correctly that in first run of your software the component is first registered before the actual program is started?

joshstechnij · ‎Nov 12, 2007

You may try adding a DoAction control event to the Finish button of the SetupCompleteSuccess dialog to run the custom action that displays the message box (setting the condition on the event to 1 if you always want it to run at the end of an install operation, or Not Installed if you only want it to run at the end of a first time install).

RobertDickau · ‎Oct 29, 2007

I think MsiSetFeatureState just wants the "leaf" feature name ("MICROSTATION_J") and not the whole subfeature tree; in MSI, internal feature names are unique, unlike features/subfeatures in InstallScript projects. You might also be able to make use of Add and Remove control events, which might save you the trouble of creating custom actions...

Online Status	Offline
Date Last Visited	‎Jan 17, 2023 05:22 PM

Re: Set msi log file name

prerequisite are skipped when running the setup for the first time

Did someine faced this problem ?

Re: Import .reg files at setup build time ?

Re: Setup prerequisite .net 2.0 framework SP1

Re: Registration of 64 bit COM components

Re: Minor upgrade and change component destination

Re: Updating RemoveFile and RemoveRegistry tables for minor upgrade

This may help...

Re: Set feature as required by Custom Action

Re: Installing components relative to INSTALLDIR

Re: Equivalent to AskPath in Basic MSI

Re: RegAsm with the /codebase argument

Re: Display MessageBox after Finish Dialog ?

Re: Using MsiSetFeatureState problem

Prerequisite – detection of Windows OS

.net framework 4.8.1 full installation .prq file ?

Update components destination which include product version

Iterate all files in Component at run time

Feature Prerequisite add properties and conditions to setup dialogs

How to create totally empty environment variable

Include links in Eula.rtf

Implement numericupdown control as in C# ?

Re: Multiple components + single component as key file

Multiple components + single component as key file