Re: [WiX-users] C# custom action to grant builtin user the installation folder full control

Deferred custom actions must be scheduled between InstallInitialize and InstallFinalize to execute within the installation transaction and thus elevated. Prefer to use PermissionExinstead of writing your own custom action. Reconsi

Re: [WiX-users] Understanding WiX elevation and BHO

On Wed, Jul 17, 2013 at 8:15 AM, Dana Epp wrote: > Execute > ="deferred" > ExeCommand='/install="[INSTALLFOLDER]$(var.Our.App.TargetFileName)" > /privileges=admin /returnExitCode=false' Impersonate="yes" /> > One reason why this CustomAction works from an elevated command prompt but not from a

Re: [WiX-users] elevated CustomAction with Impersonate = no and Execute="deferred"

On Fri, Jul 19, 2013 at 8:35 AM, Chen, Jianxin wrote: > “One reason why this CustomAction works from an elevated command prompt > but not from a non-elevated shell is that the CustomAction is scheduled > outside of the installation transaction (before InstallInitialize or after > InstallFinalize)

Re: [WiX-users] Environment variable "ProjectPath" is expanded, possible to turn off?

The build engine for Visual Studio is MSBuild. In MSBuild environment variables are accessed just like properties. The build event macros are defined as properties wix2010.targets. That's where your name collision comes in. One of the attributes that gets set on the Light MSBuild task is WixProject

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

On 8/27/13 10:05 AM, Skildum, Mathew wrote: > Here is an example of the build errors: > > CustomAction.cs(4,17): error CS0234: The type or namespace name 'Deployment' > does not exist in the namespace 'Microsoft' (are you missing an assembly > refere > nce?) > CustomAction.cs(12,58): error CS

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

On 8/27/13 11:03 AM, Skildum, Mathew wrote: > All hint paths are correct as everything build correctly in Visual Studio > (2010 and 2012). The only time it fails is when I use the 64 bit version of > MS Build. Can you provide the reference XML from the project file? I assume you have not modifi

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

t; > Here is the project file section that lists the above assembly refference: > > > > 3.5 > > > False > > ..\..\Assemblies\Powershell\System.Management.Automation.dll > True > > > > > > M

Re: [WiX-users] FileSearch issues

I'm highly suspect of the values for the Path, Depth and AssignToProperty attributes in your DirectorySearch. The example sent by John Cooper, replicated below for convenience, didn't set AssignToProperty="no" nor Depth="0".

Re: [WiX-users] using WixUI_Advanced

There must be a somewhere in your project OR in a wixlib you are referencing... You might try grep WixUI_Advanced (or equivalent) on all the files in your project and all referenced WiX projects. -- Edwin G. Castro On 8/29/13 3:34 PM, jo...@msli.com wrote: > Tracking the UIRef > > MyProject.wxs:

Re: [WiX-users] FileSearch issues

ok at, I'd > appreciate it > > Thanks, > Kai > > > > > > > On Thu, 29 Aug 2013 13:47:19 -0700, Edwin Castro wrote: >> I'm highly suspect of the values for the Path, Depth and >> AssignToProperty attributes in your DirectorySearch. &

Re: [WiX-users] Service Uninstall not Removing Service

I've had problems in the past with a service not starting as expected because of missing dependencies but never a problem uninstalling the service. I don't see anything obviously wrong here. I checked the ServiceInstall and ServiceControl documentation to double check syntax and everything looked

Re: [WiX-users] [SPAM] Re: Bootstrapper -- Can it be UI-less?

On 9/18/13 1:57 PM, Alain Forget wrote: > Gaining knowledge on how code works is fine and has value, but at the end of > the day, people have primary tasks they're trying to get done and can't > always commit the time or effort into tangential secondary tasks. I think it is clear that the WiX de

Re: [WiX-users] Getting Duplicate Entries in Add/Remove Programs

I assume you are getting duplicate entries after you attempt an upgrade. If so, how is $(var.Version) changing between upgrade attempts? Be aware that Windows Installer only takes the first THREE parts of the ProductVersion into consideration. ProductVersions 1.2.3.4 and 1.2.3.5 are the same Produ

Re: [WiX-users] Wix MSI not uninstalling files when package uninstalled

getting property changed to the right path prior to the > FileRemove entries in the uninstall log, though. I think your CA_SetCDrive custom action is scheduled too late. I thought directories needed to be set prior to CostInitiali

Re: [WiX-users] Creating two start menu shortcuts for the same executable

On 12/13/13, 3:07 PM, Markus Ewald wrote: > warning LGHT1076 : ICE69: Mismatched component reference. Entry > 'ApplicationStartMenuShortcut' of the Shortcut table belongs to > component 'ApplicationShortcut'. However, the formatted string in > column 'Target' references file 'myappl

Re: [WiX-users] Creating two start menu shortcuts for the same executable

On 12/13/13, 3:46 PM, Markus Ewald wrote: > On 12/14/2013 12:18 AM, Edwin Castro wrote: >> On 12/13/13, 3:07 PM, Markus Ewald wrote: >>> warning LGHT1076 : ICE69: Mismatched component reference. Entry >>> 'ApplicationStartMenuShortcut' of the Shortcu

Re: [WiX-users] ExeCommand will not accept any path with spaces

On 12/19/13, 5:31 PM, Gerry Reno wrote: > The relevant code section is: > > > > Execute='deferred' >ExeCommand='/k "[INSTALLDIR]"/myprogram.exe' Return='asyncWait' > /> Assuming you are trying to run something legitimate, is there a reason you are trying to wrap mypr

Re: [WiX-users] ExeCommand will not accept any path with spaces

On 12/20/13, 9:46 AM, Gerry Reno wrote: > On 12/20/2013 10:44 AM, David Connet wrote: >> > From: Gerry Reno [mailto:gr...@verizon.net] >> > > >>> >> >> > I don't think that's legal. cmd.exe is not a redistributable file. You >> > can't include it in your installer. > cmd.exe is not being di

Re: [WiX-users] ExeCommand will not accept any path with spaces

On 12/20/13, 9:49 AM, Gerry Reno wrote: > It's not a Windows program. It's a CUI program that you launch from cmd.exe Which you can still more easily start directly. If you insist in wrapping the call with cmd.exe then you MUST adhere to cmd.exe's funky quotation rules. Do it the easy way and re

Re: [WiX-users] ExeCommand will not accept any path with spaces

On 12/20/13, 10:27 AM, Gerry Reno wrote: > I not certain this will work. It might with something like a .bat file since > the system knows that .bat files are > executed by cmd.exe. > > But what is there to tell the system that my exe requires being run by > cmd.exe? Assuming that your exe is

Re: [WiX-users] Consume MSDeploy Staged Web Site Output in a WIX Installer

On Thu, Mar 14, 2013 at 2:09 PM, chennam wrote: > Is their any property setting possibility of Heat not be executed for > every build? > I don't believe so. My first thought was to modify the Condition to execute HeatDirectory only when the OutputFile does not Exists() but then it occurred to me

Re: [WiX-users] Consume MSDeploy Staged Web Site Output in a WIX Installer

DoNotHarvest controls whether the WiX MSBuild scripts will automatically harvest files in the project for you using the HeatProject task. If my memory is correct, it is set to "True" because the current implementation doesn't harvest something correctly. I think it had something to do with harvesti

Re: [WiX-users] How to use PostBuild event code to include configuration in msi name (eg MyInstaller Test.msi)

Also note that unless you change the default behavior, then '$(TargetName)' == '$(OutputName)' So, I would change the OutputName property to whatever name you need. -- Edwin On Fri, Apr 5, 2013 at 5:54 AM, Rob Mensching wrote: > Yeah, changing the TargetName should just be a matter of editi

Re: [WiX-users] Heat with file path longer than 260 chars report an error

That character limit on paths is imposed by .NET. :-( On Fri, May 3, 2013 at 10:56 AM, Marco Tognacci wrote: > I have used HeatDirectory to harvest a folder with many subdirectories and > files, but Heat.exe report an error because the filepath of an item is > larger than 260 chars (with the na

Re: [WiX-users] When are elevated permissions dropped?

See http://damianblog.com/2008/02/21/configuring-http-namespace-reservations-on-vista-using-wix/ All of the custom actions in that post are important. Note where they are scheduled to execute. -- Edwin On Fri, May 10, 2013 at 7:36 AM, Brownfield, Cory wrote: > To illustrate a problem I'm havin

Re: [WiX-users] Is is possible to change default database port?

On Mon, May 13, 2013 at 11:20 AM, John Cooper wrote: > You can pass the server/instance pair to the Server attribute. I've never > tried this with SqlDatabase, but can you pass the server/instance,port? > I would expect server,port to work as well. -- Edwin G. Castro --

Re: [WiX-users] Putting File in TempFolder - Nothing Happens

The custom action will execute before file copy if it is an immediate custom action rather than deferred. -- Edwin G. Castro On Tue, May 28, 2013 at 7:05 AM, Pally Sandher wrote: > >From your InstallExecuteSequence code it looks like the Custom Actions > should be called after the file is writt

Re: [WiX-users] *Package Permanent attribute

My understanding is that a Bundle is processed by the "burn" engine. ARP == Add/Remove Programs On Fri, May 31, 2013 at 12:44 PM, Alain Forget wrote: > By "burn", you mean what I'm referring to as the Bundle? > > And by ARP, you mean "Add/Remove Programs"? > > Just making sure I understand. :-

[WiX-users] Predicting Bootstrapper Cache Location

Is there a way to predict the cache location for my bootstrapper so I can pass it to my MSI in public property? I need to set a registry value with the uninstall command for my bootstrapper (similar to the ARP UninstallCommand) but I'm having a hard time guessing the cache location for the bootstra

Re: [WiX-users] Predicting Bootstrapper Cache Location

Jacob, You mentioned something interesting that I can't get to work. I tried But BUNDLEPROVIDERKEY is always empty in the msi log. Should I expect that to work? -- Edwin G. Castro On Thu, Mar 26, 2015 at 7:52 AM, Hoover, Jacob wrote: > To extend upon Phil's suggestion, > http

Re: [WiX-users] Predicting Bootstrapper Cache Location

NE_BUNDLEPROVIDERKEY]" > Execute="firstSequence" /> > ... > >After='AppSearch'>CMDLINE_BUNDLEPROVIDERKEY > > -Original Message- > From: Edwin Castro [mailto:egca...@gmail.com] > Sent: Thursday, March 26,

Re: [WiX-users] Predicting Bootstrapper Cache Location

The remarks at http://wixtoolset.org/documentation/manual/v3/xsd/dependency/providerkey.html say This provider key is designed to persist throughout compatible upgrades so that dependent bundles do not have to be reinstalled and *will not prevent your product from being upgraded*. If this attribut

[WiX-users] Which Process Executes Custom Actions

I have two custom action functions (A and B) that use LoadLibraryEx() to load a DLL that already exists on the target system (NOT installed by my MSI) and then proceeds to call a few functions in that DLL. My MSI is installed by the WiX Standard Bootstrapper. These custom actions functions in a tot

[WiX-users] Modifying Request State

I'd like to install or uninstall an ExePackage whenever an MsiPackage is selected for install or uninstall. Details: * ExePackage must be installed whenever MsiPackage is selected for install. * ExePackage must be installed before MsiPackage is installed. * ExePackage must be uninstalled whenever

Re: [WiX-users] Modifying Request State

It occurs to me that I don't want to change the ExePackage's request state. Rather I want to change it's action state to the same action state selected for the MsiPackage. Is there a way to get and set package action state? On Thu, Apr 2, 2015 at 2:14 PM, Edwin Castro wrote:

[WiX-users] Customizing Standard Actions

I work at a security company and one of our products provides additional protection beyond built-in access controls in Windows. The end result of all of this additional protection is that the installer I'm maintaining cannot simply use some of the built-in tables/actions in Windows Installer becaus

[WiX-users] Modifying new msi package prior to recache in a custom action

I’m trying to recache one of a number of packages before RemoveExistingProducts. My custom action extracts the new package from the Binary table, then attempts to MsiOpenDatabase() to update the new package’s ProductCode and ProductVersion to avoid needing a new package for each instance we’re tryi

Re: [WiX-users] Modifying new msi package prior to recache in a custom action

I'll provide more details. I inherited the installer codebase for a product that has released twice (A, B) and was almost ready to release again (C). Releases A and B have poorly written custom actions that cause them to fail occasionally (say 5% of the time) while they are getting uninstalled as p

Re: [WiX-users] Duplicate files from multiple locations

Unfortunately, you'll need to address the duplication yourself. The MSI database schema doesn't allow for primary keys to be duplicated. Years ago, when I was using HarvestDirectory, I wrote some XSLT transforms to either remove duplicates or modify/set File/@Id to avoid duplication. I also had

Re: [WiX-users] HavestDirectory -svb6

You could try setting the HarvestDirectoryAdditionalOptions property in your *.wixproj file. Something like this: -svb6 -- Edwin G. Castro On Tue, Jun 9, 2015 at 2:18 PM, Brad Woodfiel wrote: > With the Heat command there is an option '-svb6' for when dealing with dll > and ocx files crea

[WiX-users] Getting WixBundleLog Timestamp

Is there a way to get the timestamp used in the WixBundleLog? I'd like to use it as part of the log filename in the InstallCommand and/or UninstallCommand of the ExePackages in my Bundle. -- Edwin G. Castro -- ___

[WiX-users] How to Allow Same Version Upgrades in Bundles

I'm trying to implement same version upgrades in our bootstrapper. We build our product in one build process and later create the installers in a second package process. This allows us to repackage our product when fixing installer changes that do not affect the product in any other way. We do not

Re: [WiX-users] How to Allow Same Version Upgrades in Bundles

does not. > > _ > Short replies here. Complete answers over there: > http://www.firegiant.com/ > > > -Original Message- > From: Edwin Castro [mailto:egca...@gmail.com] > Sent: Tuesday, June 23, 2015 1:58 PM > To: General discus

[WiX-users] How to Uninstall ExePackage Only During Uninstall

My ExePackage gets uninstalled during upgrades and I'd like to only uninstall during an actual uninstall. Any suggestions on how I might go about doing this? I was hoping I could do something in my bafunctions.dll but I'm hitting a wall in my brainstorming. My bundle consists of the following: * A

Re: [WiX-users] Error 0x80070057: Failed to parse @Code value: -1

I forgot to mention that I'm using WiX 3.8.1128.0. On Thu, Jul 2, 2015 at 5:07 PM, Edwin Castro wrote: > Our bundle fails to install when our product is built with bullseye for > code coverage. The bundle log is not created. Instead > Setup_timestamp_Failed.txt is created an

[WiX-users] Error 0x80070057: Failed to parse @Code value: -1

Our bundle fails to install when our product is built with bullseye for code coverage. The bundle log is not created. Instead Setup_timestamp_Failed.txt is created and contains the following: [04AC:0744][2015-07-02T14:59:01]e000: Error 0x80070057: Failed to parse @Code value: -1 [04AC:0744][2015-0

Re: [WiX-users] Error 0x80070057: Failed to parse @Code value: -1

ExitCodeInfo.cs:38:this.Code = > unchecked((uint)value).ToString(); > _ > Short replies here. Complete answers over there: > http://www.firegiant.com/ > > > -----Original Message- > From: Edwin Castro [mailto:e

Re: [WiX-users] Error 0x80070057: Failed to parse @Code value: -1

I see the fix in wix39rtm. WiX 3.9 and Bullseye appear to work better together. We're going to recommend upgrading to WiX 3.9. On Fri, Jul 3, 2015 at 8:54 AM, Rob Mensching wrote: > I was looking at HEAD. Bug fix in WiX v3.9 or v3.10? > >

[WiX-users] CabExtract returns 0x80070003

I'm trying to use CabExtract from cabutil.h (WiX v3.9) but I always get hr == 0x80070003 (The system cannot find the path specified). My code is equivalent to the following: hr = CabInitialize(false); hr = PathCreateTempDirectory(NULL, L"extract", 1, &tempDir); hr = PathConcat(tempDir, L"file.c

Re: [WiX-users] CabExtract returns 0x80070003

then the fix is to ensure the directory portion of wzPath exists before calling CreateFileW. On Thu, Jul 9, 2015 at 10:34 PM, Edwin Castro wrote: > I'm trying to use CabExtract from cabutil.h (WiX v3.9) but I always get hr > == 0x80070003 (The system cannot find the path specified)

[WiX-users] Why Does Bundle Prompt For Source During Uninstall?

I have a bundle that I have successfully installed. When I try to uninstall I get the following: [0E54:03D0][2015-07-13T15:34:03]i300: Apply begin [07F0:0814][2015-07-13T15:34:03]i360: Creating a system restore point. [07F0:0814][2015-07-13T15:34:10]i361: Created a system restore point. [0E54:01C4

[WiX-users] RemoveExistingProducts does not set MsiLogFileLocation

I know this is now a WiX specific question. Please point me to a better place to ask this. I have a custom action that launches an exe. The custom action uses MsiLogFileLocation as a base to construct a log file path for the exe command line. This all works great during install and uninstall becau

[WiX-users] Possible Bug: RegDelete does not work properly with REG_KEY_32BIT on a 64-bit system

I was trying to use RegDelete from the dutil library and I noticed my 32-bit key did not get deleted on a 64-bit system. I think the problem is the following RegOpen call hr = RegOpen(khRoot, wzSubKey, KEY_READ, &hkKey); if (E_FILENOTFOUND == hr) { ExitFunction1(hr = S_OK); } Since KEY_WOW64_

Re: [WiX-users] Possible Bug: RegDelete does not work properly with REG_KEY_32BIT on a 64-bit system

I can't use semi-custom-actions for this particular piece of work because I need to call an API to get permission to create, delete, or modify these particular registry keys. I work at a security company where they have implemented additional security features through drivers that disallow normal i

[WiX-users] Localization and acceleration key combinations in WixStandardBootstrapperApplication

I'm using WixStandardBootstrapperApplication.HyperlinkSidebarLicense in my burn bundle. I have localized strings for a few languages. I'm looking into a bug reported against our Spanish localization. The expectation is that when the Alt + A is pressed, the focus would be received by the EULA checkb