Re: [WiX-users] Write STX (Start of Text / ASCII 2) to a registry string

Yup, I ended up doing that, I would have liked to keep the value type as string but this will suffice. Thanks, Keith Moore > -Original Message- > From: robert_h_yang [mailto:robert_y...@non.agilent.com] > Sent: Tuesday, 20 December 2011 5:06 AM > To: wix-users@lists.sourceforge.net > Sub

[WiX-users] bootstrapper help

I'm trying to create a bootstrapper that checks for and installs the .net framework 4.0 client profile. (I don't want to ship the 42MB .net installer, prefer dl&install)I also want to log the warnings and errors of the msi on all installs, so I can provide them in error reports. So, how do

Re: [WiX-users] WiX 3.6 major upgrade backup and restore

That's really a function of when you schedule RemoveExistingProducts (which is handled by the Schedule attribute in the MajorUpgrade element). Read the descriptions for "Schedule" and see which one fits the model of deployment you want. If you want the old install to remain if the upgrade fail

[WiX-users] WiX 3.6 major upgrade backup and restore

I have written custom actions that backup and restore user-managed files and folders associated with my application's operation. The Setup.wxs file uses the MajorUpgrade tag. What InstallExecuteSequence entries would invoke the Backup custom action before an upgrade and the Restore action after an

Re: [WiX-users] Write STX (Start of Text / ASCII 2) to a registry string

Have a look at Type="binary" (REG_BINARY), eg. -Rob Keith Moore wrote > > Is there a way to write a the STX character to the registry? I am using > Wix 3.5. > > I have the registry import file below: > - > Windows Registry Editor Version 5.00

Re: [WiX-users] How to register OLE server?

Heat cannot currently harvest EXE servers. I ended up writing a custom Heat extension, since we have a lot of legacy COM objects, some of which have special dependencies, such as ATL.DLL. We also have a postprocessor step to fix the component GUID's to be consistent from build to build (among oth

Re: [WiX-users] References for installation Best Practices

Replying to my own message... it seems that the issue of what to do with per-user config during uninstallation is a well-known and thorny one. Best practice seems to be to leave it behind on the machine, such that it will still be there should the user re-install the application (or a later versio

[WiX-users] Bootstrapper FailIf message is not displayed

Hello All, In our bootstrapper we are using a RegistryCheck to check a registry value and save the value in property PENDING_RENAME. If the value exists, the bootstratpper should fail and display an error message. The FailIf statement is shown below: When the value exists, the check fai

[WiX-users] Adding the configSections element to a web.config file as the first child element

I’m using XmlConfig to modify an existing web.config that does not have a configSections element defined so I am adding it. Works great, except it is adding it to the end of the document. Anyone know of a way I can add it as the first child element (per the ASP.Net web.config requirements)? Tha

Re: [WiX-users] WiX3.6 uninstall previous version

Read up on the MajorUpgrade element in the Wix Schema documentation. If you use this element, and your installers follow the component rules, the major upgrade should remove the existing product for you and install the upgrade in its place. I am unaware of any significant differences in uninst