Re: [WiX-users] Solved! RE: RegistrySearch returning strange value

thing like that) error dialog. Bill -Original Message- From: Arnette, Bill [mailto:bi...@signalscape.com] Sent: Friday, February 15, 2013 12:53 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Solved! RE: RegistrySearch returning strange value That

Re: [WiX-users] Solved! RE: RegistrySearch returning strange value

2:34 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Solved! RE: RegistrySearch returning strange value That's correct. -Original Message- From: Arnette, Bill [mailto:bi...@signalscape.com] Sent: 15 February 2013 16:55 To: General discussion for Window

Re: [WiX-users] Solved! RE: RegistrySearch returning strange value

: Re: [WiX-users] Solved! RE: RegistrySearch returning strange value Yep, the Canon installers are the scourge of the deployment world ;) Us too. Sorry I didn't see your message in time. http://kb.sdl.com/#tab:homeTab:crumb:7:artId:4654 -Original Message- From: Arnette, Bill [mail

[WiX-users] Solved! RE: RegistrySearch returning strange value

it is searching or at what path it found a valid value? That would have helped tremendously in this case. -Original Message- From: Arnette, Bill [mailto:bi...@signalscape.com] Sent: Wednesday, February 13, 2013 11:42 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] RegistryS

[WiX-users] RegistrySearch returning strange value

Hi all, I ran into the strangest problem on a customer's machine today. He was installing a new version (MAJOR upgrade) of our software which has the authoring below. We set INSTALLDIR from UPGRADEDIR if a previous version is installed (SetUpgradeInstallDir custom action) and make the insta

Re: [WiX-users] Heat.exe, "suppress COM" usage (-scom)

Use -scom -sreg to suppress all COM and registry info if you are only after file information. -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Tuesday, January 08, 2013 4:29 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-user

Re: [WiX-users] Registry search and condition message in installer

Wouldn't your x86 search need to search the WoW6432Node of HKLM to be correct? HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall But also, it seems to me that you should be using the MSI API (MsiGetProductInfo specifically) in a custom action to get information about other in

[WiX-users] How to handle flavor upgrades

What would be the recommended way to handle "flavor" upgrades such as from an Express version of an application to a Pro version? --**-- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addresse

Re: [WiX-users] Intentionally leaving a file behind...

Mark the component as permanent and never-overwrite. -- Bill Arnette www.starwitness.com From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rory Clark Sent: Tuesday, August 21, 2007 4:57 PM To: wix-users@lists.sourc

Re: [WiX-users] backing up the existing files while installing

We tried to do this with our configuration files. The issue we faced was that because RemoveExistingProducts came early on, the old file was removed with the old product, but we wanted it remain untouched by the installer during an upgrade or if the user manually uninstalled the application.

Re: [WiX-users] AppSearch during UI

ling the old version first. -- Bill Arnette www.starwitness.com -Original Message- From: Brian Simoneau [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 31, 2007 2:15 PM To: Arnette, Bill; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] AppSearch during UI You could write a perm

[WiX-users] AppSearch during UI

We are trying to mitigate an admittedly pathological case during installation. 1. User installs application to other than default directory. The installation installs a permanent, never-overwrite configuration file which (among other things) specifies a file store [1] path which is specified by

Re: [WiX-users] bootstrapper?

I think there is a package for SQL Server Express for the VS 2005 bootstrapper. I am not sure how to specify it in an MSBuild file, but you may be able to figure that out by creating a dummy setup in VS 2005 and specifying it as a dependency and then looking at the project file. You can also crea

Re: [WiX-users] Error code 2753?

Installed is the CURRENT state of the installation. I.e. You are telling that CA to run only if the applications is currently installed (i.e. you are uninstalling it). You want 'NOT Installed' for your condition. -- Bill Arnette www.starwitness.com -Original Message- From: [EMAIL P

Re: [WiX-users] Conditionally edit XML file if it is installed

table. I guess I'll just have to use that method instead of the conditionalizing on the XML file component state or action. -- Bill Arnette www.starwitness.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arnette, Bill Sent: Thursday, July 19, 2

Re: [WiX-users] Conditionally edit XML file if it is installed

make sure that INSTALLDIR is resolved before the AppSearch, but still nothing. Note that I am using WiX v2 if that matters. -- Bill Arnette www.starwitness.com -Original Message- From: Pierson Lee (Volt) [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 11:59 AM To:

[WiX-users] Conditionally edit XML file if it is installed

I am trying to have my installer edit an XML file after it is installed. However, the XML file should not be installed or edited if it already exists on the system. So I am trying to condition the installation of the XML editing component on the state/action of the component which contains the XM

Re: [WiX-users] Setting icons to shortcut, works with exe but not with ico

See the last paragraph in the Icon Table documentation [1]: --- However, Icon files that are associated with shortcuts must be in the EXE binary format and must be named such that their extension matches the extension of the target. The shortcut will not work if this rule is not followed. For exa

Re: [WiX-users] What exactly is SourceDir?

The default value for TARGETDIR [1] is C:\ but tools like VS.NET setup and deployment projects add a type 51 CA (set property from formatted text) to set TARGETDIR to [ProgramFilesFolder][Manufacturer]\[ProductName]. Also TARGETDIR can be specified on the command line to specify where you want

Re: [WiX-users] Shortcut targeting file in a different component?

Try Target="[#Life_Balance.exe]" in the shortcut element. -- Bill Arnette www.signalscape.com > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Stuart A. Malone > Sent: Wednesday, March 21, 2007 3:27 PM > To: wix-users@lists.sourceforge.net >

Re: [WiX-users] vs. CA

You would have to do a custom action to set the property from a property and you can condition the execution of that. MYOLDVER From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Levi Wilson Sent: Thursday, January 25, 2007 11:53

Re: [WiX-users] Running a file after installation

2 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Running a file after installation > > > Hi! > Thanks for your help, but now I got this message when I try > to light my > wixobj file. > > error LGHT0112 : Unresolved reference to symbol 'Directory:INSTALLDIR

Re: [WiX-users] Running a file after installation

Two suggestions: 1) Pass the path to the batch file on the batch file invocation command line and then CD to that path in the script. And then in your my.bat file: Rem Gets the path of my .bat file from the command line Set MYPATH=%1% Rem CD to my path Cd /D %MYPATH% Rem Ru

Re: [WiX-users] Installed: Local; Request: Absent; Action: Null ?

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > André Pönitz > Sent: Thursday, December 21, 2006 3:20 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Installed: Local; Request: Absent; > Action: N

Re: [WiX-users] Installed: Local; Request: Absent; Action: Null ?

Non-Windows Installer installers use the SharedDlls registry key to refcount the usage of common/shared dlls. By default Windows Installer will only increment that refcount if it already exists so that the other installer will track the refcount properly if a WI installer installs the same file

Re: [WiX-users] Renaming a file during installation

You're probably better off either: A) Copy the file from the template in a custom action. OR B) Have the application copy the file from the template to the user's application data folder if it doesn't already exist. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTEC

Re: [WiX-users] question

that? > -Original Message- > From: Bob Arnson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 22, 2006 4:43 PM > To: Mike Dimmick > Cc: Arnette, Bill; wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] question > > Mike Dimmick wrote: > > It may well have p

[WiX-users] question

Why does Wix.chm say this about Verb/@Target? Target file to be executed for the verb. The value should be a formatted Property to refer to the *short path to the file*, for example: [!TargetFileId]. Only valid for non-Advertised verbs. I see no such restriction in the Platform SDK docs

Re: [WiX-users] way to create merge module and avoiding codeduplication

> Sent: Wednesday, November 15, 2006 7:08 PM > To: Arnette, Bill > Cc: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] way to create merge module and > avoiding codeduplication > > Arnette, Bill wrote: > > A merge module should never deliver a componen

Re: [WiX-users] way to create merge module and avoiding codeduplication

If you do that, how do you resolve it against this: http://msdn2.microsoft.com/en-us/library/aa368034.aspx: A merge module should never deliver a component containing system files to the main feature of an application, because this may cause the Installer to validate and repair the application eac

Re: [WiX-users] Property name to be used in MsiGetProperty

Forgot to add this link: http://msdn.microsoft.com/library/en-us/msi/setup/obtaining_context_info rmation_for_deferred_execution_custom_actions.asp?frame=true > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Arnette, Bill >

Re: [WiX-users] Property name to be used in MsiGetProperty

Your CAs are all deferred so there is a very small subset of properties you can get with MsiGetProperty. Parameters are passed to deferred custom actions in a property called CustomActionData. To set CustomActionData, you have to use another custom action to set a property with the same name as t

Re: [WiX-users] Multiple parameters in CA dll

An immediate custom action has access to the property table, so put your parameters in properties and use MsiGetProperty to retrieve them in your CA. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bahar ShahSent: Friday, November 03, 2006 9:44 AMTo: wix-users@

Re: [WiX-users] CustomAction not being called

Make sure that is the entry point of the DLL. An exported __stdcall function is actually decorated to be [EMAIL PROTECTED] so try setting DllEntry to [EMAIL PROTECTED] If that works, you can alias the export with the with /EXPORT:[EMAIL PROTECTED] option on the linker command line. Use: dumpbin

Re: [WiX-users] Install with prevous versions

the UI stage, and it will > probably bite you on Vista because you probably won't have > the required > privilege in the UI sequence (with UAC you'll be a standard > user; in the > execute sequence you'll be elevated). > > > Phil Wilson > > >

Re: [WiX-users] Install with prevous versions

I don't think there are any path manipulation capabilities in MSI, so you'll have to write a CA that sets INSTALLDIR from OLDINSTALL3 or OLDINSTALL4. You can set a property in a CA if it is an immediate (not deferred) CA using MsiSetProperty. Set the CA's @Execute attribute to 'oncePerProcess'

Re: [WiX-users] [NAnt-users] "Error loading GUID..." when using task forVS2005

Drat! Did it again. Sorry. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Arnette, Bill > Sent: Tuesday, October 17, 2006 2:23 PM > To: Kumar .S; wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] [NAnt-users

Re: [WiX-users] [NAnt-users] "Error loading GUID..." when using task forVS2005

] http://nantcontrib.sourceforge.net/ [2] http://nantcontrib.sourceforge.net/release/latest/help/tasks/msbuild.htm l From: Kumar .S [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 1:52 PM To: Arnette, Bill Subject: Re: [NAnt-users] "Error lo

Re: [WiX-users] [NAnt-users] "Error loading GUID..." when using task forVS2005

ving to VS 2005. Please I am not a extensive user of nant. I have little time, so I request you for a sample script. Please.   Regards, Kumar  On 10/17/06, Arnette, Bill <[EMAIL PROTECTED]> wrote: Nant does not support VS 2005 solution files ye

Re: [WiX-users] [NAnt-users] "Error loading GUID..." when using task forVS2005

ttle time, so I request you for a sample script. Please.   Regards, Kumar  On 10/17/06, Arnette, Bill <[EMAIL PROTECTED]> wrote: Nant does not support VS 2005 solution files yet.  Use the taskto call msbuild on VS 2005 solution files. > -Original Me

Re: [WiX-users] WixUI LGHT0103

It is a PowerShell issue.  I have do to the same quoting when using NAnt when I want to pass a property on the command line.  Ex. Nant -D:property=value  in cmd.exe has be typed in PowerShell as Nant "-D:property=value".  Thinking about it, it may have to do with how it parses the command li

Re: [WiX-users] Installing machine-specific license files

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Sigurd Stenersen > Sent: Monday, October 02, 2006 6:22 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Installing machine-specific license files >

Re: [WiX-users] Installing machine-specific license files

ssage- From: Bob Arnson [mailto:[EMAIL PROTECTED]] Sent: Thu 9/28/2006 9:50 PM To: Arnette, Bill Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing machine-specific license files Arnette, Bill wrote: > So my plan is to create a WiX project that the licensing system builds &g

[WiX-users] Installing machine-specific license files

Our licensing system is similar to Windows Product Activation in that a hash is created for the machine the software is licensed on, sent to us, and we return a self-extracting executable that installs a bunch of license files that are generated for that specific machine. What this means is that

Re: [WiX-users] How to create single installable exe

You can create a self-extracting executable with something like WinZipSE. I have been using a free self-extacting executable creator called Zip2SecureExe [1].   You can also use IExpress which ships with Windows XP.  Just type IExpress in the Start->Run... box and follow the wizard.   [1] ht

Re: [WiX-users] how to get parent directory of a folder

If you are installing based on an already installed product, don't let the user browse to the installed location; they may get it wrong or not know where it's installed.  Instead, use a registry or directory search to find where the installed application resides and set the path in a propert

Re: [WiX-users] My Installer Requirements

It does have to do with WiX. WiX is what generates the MSI database. MsiInstallProduct() is an API function that you can call from a program to install an MSI database. In fact, that is, among other things, exactly what msiexec.exe does. Internally it calls MsiInstallProduct to install the MSI y