About loralynne

loralynne · ‎Sep 07, 2010

Although that works for a UI install, it doesn't work for a silent install since the UI sequence doesn't get executed during a silent install.

loralynne · ‎Sep 07, 2010

What I did that works for me was add a Set Directory custom action with the following settings: Directory Name: INSTALLDIR Directory Value: [ProgramFiles64Folder]\MyCompany\MyProduct Execution Scheduling: Execute only once Install Exec Sequence: After CostFinalize Install Exec Condition: Not Installed And VersionNT64 And ISReleaseFlags="64bit" My 64-bit Product Configuration has a release flag called 64bit; hence, the ISReleaseFlags="64bit" in my Install Exec Condition. With this custom action, my 64-bit installer installs to Program Files for both a UI install and a silent install.

loralynne · ‎Sep 02, 2010

Anyone have any input on this? Is there a way I can delete a whole section from an INI file?

loralynne · ‎Aug 30, 2010

In my Basic MSI project, I created a component with no files in it, just an ini file change associated with it. I marked the component as permanent since the .ini file that I need to edit is in [SystemFolder]. I added a section and keyword/value pairs in the INI File Changes view. These ini entries don't get created by the installer, but rather get generated by the app that gets installed. During uninstall, these entries need to be removed from the .ini file, so I set the action for the keyword to "Remove Whole Value". When I do an uninstall, the ini file gets deleted. Is this a known issue? How do I delete a whole section and a keyword/value pair from an ini file during uninstall? Any help would be greatly appreciated. Thanks, Lora

loralynne · ‎Aug 25, 2010

Right, it be would be great if those two issues could be fixed. Here are more details of the issue I'm having, just fyi. For my IS2009 project, my setup was compiled as Unicode. When I run it on a Japanese (or probably any other double-byte language) machine and the prerequisite files are extracted, the strings "för" and "für" in the prerequisite filename would show up as "f・ ", but the installation continues with no error. (This is the same result as my ANSI setup created with IS2008.) But after converting to IS 2010 with the setup launcher still set to Unicode, I get the 1152 error when running setup.

loralynne · ‎Aug 24, 2010

This 64-bit setup.exe request stems from this Microsoft article: http://msdn.microsoft.com/en-us/library/aa372396%28v=VS.85%29.aspx where it says "When using a bootstrapping application to install a 64-bit Windows Installer Package, compile the bootstrapping application as a 64-bit application." It's obviously not a requirement, rather a guideline. Some of the prerequisites in my setup are for both my 32-bit release and 64-bit release, so I don't condition them for a specific architecture and thus, they get installed when doing a silent installation. I would say it makes more sense to add a way to install either a 32-bit or a 64-bit version of the MSI as part of the same setup.exe. However, there may be customers who want to install 32-bit on a 64-bit machine for whatever reason. So maybe there could be an option in IS that, if turned on, would display a message to the end-user running on a 64-bit machine asking if they would like to install the 32-bit version or the 64-bit version. If the option is turned off, the 64-bit version gets installed by default.

loralynne · ‎Aug 24, 2010

Thanks, Michael. Not sure if you're aware...having extended ASCII characters in the prerequisite name wasn't a problem in IS2009 or IS2008. It's unfortunate that I'll have to change it to not have high ASCII characters now considering that the previous versions of our product had the technically correct prerequisite name. -Lora

loralynne · ‎Aug 23, 2010

Can support be added for setup.exe to be compiled as a 64-bit app for Product Configurations whose Template Summary contains x64 or Intel64? Then, if a project includes setup/feature prerequisites and the end user attempts to run the 64-bit setup.exe on a 32-bit machine, setup.exe would display an error message saying that the processor type is not supported and nothing, including the prerequisites, gets installed. Thanks, Lora

loralynne · ‎Aug 23, 2010

Anyone have any input on this? To put it another way, is there a way that setup.exe can tell 1) if it's associated with my 32-bit msi or my 64-bit msi AND 2) what the processor type of the target machine is? Thanks, Lora

loralynne · ‎Aug 23, 2010

Thank you for your response, Michael. My prerequisites actually have the Build Location set to Copy from Source Media, but are you saying that this shouldn't be a problem? Or do I have to upgrade to IS2011, and then it won't be a problem there? Just to clarify, it's the name of my .prq file that has the ü in it, not the installer for the prerequisite. Thanks again, Lora

loralynne · ‎Aug 23, 2010

Hi, I'm having the same problem. If I don't have the option of renaming the file (which contains a "ü") or switching from a Unicode setup.exe to an ANSI setup.exe, what can I do to work around this? Also, is this going to be fixed in IS 2011? Thanks, Lora

loralynne · ‎Aug 20, 2010

I have a basic MSI project that has both a 32-bit product configuration and a 64-bit product configuration (each with a setup.exe). Both configurations have the same set of prerequisites which include 32-bit installers. Although 64-bit apps can't run on 32-bit machines, one of our test cases is to attempt to run the 64-bit installer on a 32-bit machine. Running setup.exe for the 64-bit installer non-silently on a 32-bit machine displays the error dialog "This installation package is not supported by this processor type..." as expected, and neither the prerequisites nor the main product get installed. However, when it is run silently, the prerequisites do get installed (unexpected behavior), but not the main product (expected behavior). Is there a way I can conditionalize the prerequisites such that they get installed in the following scenarios: - the bootstrapper for my 32-bit installer is run on 32-bit machines - the bootstrapper for my 32-bit installer is run on 64-bit machines - the bootstrapper for my 64-bit installer is run on 64-bit machines but not when the bootstrapper for my 64-bit installer is run on 32-bit machines? Again, this problem only happens during a silent install. Any help would be greatly appreciated. Thanks, Lora

loralynne · ‎Apr 14, 2010

That's exactly what I'm looking for. Thanks so much, Debbie.

loralynne · ‎Apr 14, 2010

I have both 32-bit components and 64-bit components in my project. My 64-bit release includes both the 32-bit components and the 64-bit components. I have a CA that sets the INSTALLDIR to ProgramFiles64Folder, and it has the condition VersionNT64. I build my 32-bit release, and it runs as expected on a 32-bit machine. When I run it on a 64-bit machine, it executes the CA that sets INSTALLDIR to ProgramFiles64Folder since the condition VersionNT64 is met. However, I don't want this CA to be executed when I run my 32-bit installer on a 64-bit machine. I only want it to be executed when I run my 64-bit installer.

loralynne · ‎Apr 13, 2010

Thanks for your response, Dan. That's actually exactly what I have, and I believe Clark had this same problem also. This won't work since a 32-bit installer run on a 64-bit machine will change INSTALLDIR to ProgramFiles64Folder, which is not I want. I want this custom action to be executed only for my 64-bit installer, so I need to condition this CA as such. For my 32-bit Release, I have a release flag called 32bit and for my 64-bit Release, I have a release flag called 64bit. I was hoping I could use the 64bit release flag for this CA.

Online Status	Offline
Date Last Visited	‎Mar 19, 2020 05:40 AM

Re: 64 bit vs 32 bit Installation Support?

Re: 64 bit vs 32 bit Installation Support?

Re: Deleting sections and keywords from an .ini file

Deleting sections and keywords from an .ini file

Re: Error 1152 in Chinese

Re: 64-bit setup.exe

Re: Error 1152 in Chinese

64-bit setup.exe

Re: Prerequisites, processor type, and silent installation

Re: Error 1152 in Chinese

Re: Error 1152 in Chinese

Prerequisites, processor type, and silent installation

Re: 64 bit vs 32 bit Installation Support?

Re: 64 bit vs 32 bit Installation Support?

Re: 64 bit vs 32 bit Installation Support?

Re: Delete generated files during rollback

Delete generated files during rollback

Re: 64-bit setup.exe

Re: Patching existing applications using a newer digital signature

Re: IIS: Installing a web site if port is already taken

Re: 64 bit vs 32 bit Installation Support?

Re: Silent Install with Feature Prerequisites

Re: Silent Install with Feature Prerequisites

Re: Silent Install with Feature Prerequisites

Re: Silent Install with Feature Prerequisites