Re: [WiX-users] bootstrapper for uninstallation?

MSI 4.5 and later allow adding additional product/package transactions from the MSI itself (via custom actions calling APIs). If you can require MSI 4.5 you can accomplish this without resorting to ARPSYSTEMCOMPONENT. You do have to write small bootstrapper exes that call certain APIs to use this m

[WiX-users] Upgraded from 3.0 to 3.5

Geeting this error: Error 61 Unresolved reference to symbol 'CustomAction:InstallExecuteSequence/CAInstallVoyagerDatabase.Install' in section 'Product:{353CAAFF-C714-44B8-A522-F768DDC967CC}'. -- Bhaumik Barot -- This SF.

[WiX-users] bootstrapper for uninstallation?

Hi, Now I come to the uninstall part. When install my product, I have a bootstrapper, that install an external product first as the prerequisite, and then invoke my own MSI. When uninstall my product, I also need to uninstall the external product after uninstall my MSI. The command I used to un

[WiX-users] RemoveExisting Products failing with /qn upgrade

Does any know why the RemoveExistingProducts action would fail when an upgrade is run silently? If I run in full UI mode, everything works as expected. If I run the upgrade with /qn, the RemoveExistingProducts does not work and I end up with both products installed on the system. RemoveExistingP

Re: [WiX-users] Custom Action not running

The underlying issue is likely to be that UAC systems run impersonated custom actions without elevation, even if you are an administrator. ON XP your custom action would be running elevated with admin privs, but not on UAC, and that's why Blair is telling you how to make it elevated. Phil Wils

Re: [WiX-users] Including referenced assemblies with a Project Output Group

Yeah, unfortunately. There are just too many bugs in the feature to sort it all out in any reasonable time frame to finish WiX v3.5 (which is taking longer than hoped already, gosh dang IIS7 bugs). On Fri, Jul 16, 2010 at 9:56 AM, Neil Sleightholm wrote: > For info I raised a bug for this issue a

Re: [WiX-users] Custom Action not running

For starters, the action must be scheduled between InstallInitialize and InstallFinalize, and must be marked as Execute="deferred" with Impersonate set to "no". Of course, at that point, the custom action does not have direct access to the database or most session properties. This smells like "sel

Re: [WiX-users] Porting installer to WiX

True.  Though depending on the size of the package taking a quick look at the log is faster and gives you the original MSI with it's storage intact.  It also doesn't require you to drop to the command prompt to pass in a /v"/a".   - Original Message From: Michael Urman To: General discu

Re: [WiX-users] Including referenced assemblies with a Project Output Group

For info I raised a bug for this issue and I think it has been moved out to v4. Neil Neil Sleightholm X2 Systems Limited n...@x2systems.com From: Stelios Kyprou [mailto:stelios.kyp...@formicary.net] Sent: Fri 16/07/2010 15:04 To:

Re: [WiX-users] Custom Action not running

I did look at DifxApp, but for this particular application, I feel it would be best to use the application launched from the custom action being called for reasons that I won't go into as they are specific to the particular application. Is there a way to give the custom action the necessary pri

Re: [WiX-users] Custom Action not running

Not sure what your logging problem would be, but I suspect that your custom action does not have the necessary privilege to install drivers. Have you looked at DifxApp? -Original Message- From: Thode, Katelyn [mailto:katelyn.th...@guidancesoftware.com] Sent: Friday, July 16, 2010 8:17 AM

Re: [WiX-users] Porting installer to WiX

Thanks - that worked perfectly! -Original Message- From: Michael Urman [mailto:mur...@gmail.com] Sent: Friday, July 16, 2010 10:05 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Porting installer to WiX While extracting it from the temp folder, or t

[WiX-users] Custom Action not running

I am in the process of testing my installer on different operating systems. The installer was created using 32-bit XP. Everything works as expected and the Custom Action is run. The exit dialog states that the application has been installed. When I try running the installer on 32-bit Vista,

Re: [WiX-users] Porting installer to WiX

While extracting it from the temp folder, or the cached location mentioned in a log file will work, why not just perform an administrative install? This way you can drop the .msi file wherever you'd like. http://helpnet.flexerasoftware.com/robo/projects/installshield12helplib/IHelpSetup_EXECmdLine

Re: [WiX-users] Porting installer to WiX

Run the EXE and when the dialog displays - leave it open an search your temp folder for the newest folder and files. The msi should be in there someplace -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Thursday, July 15, 2010 5:03 PM To: General discussion f

Re: [WiX-users] Include an optional file in installer duringcompile/link

Great - that did the trick! Thanks, Beth -Original Message- From: i...@roadrunner.com [mailto:i...@roadrunner.com] Sent: Thursday, July 15, 2010 4:59 PM To: General discussion for Windows Installer XML toolset. Cc: Beth Hechanova Subject: Re: [WiX-users] Include an optional file in insta

Re: [WiX-users] Including referenced assemblies with a Project Output Group

Unfortunately no... By default 3.5 will not include this feature. I asked this question a while ago, and this is the replies i got from John Robbins and Rob Mensching: FYI: given the issues with auto-harvesting in WiX v3.5, that feature will be disabled before shipping. We'll try to bring it back

Re: [WiX-users] Porting installer to WiX

You'll need the UpgradeCode but I don't think you'll need the ProductCode since your new installer will need a new one to do a Major Upgrade.   Otherwise I think you are taking an excellent approach.   Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or re

Re: [WiX-users] Porting installer to WiX

Thanks - I do have it all ported over without looking at the previous source code. I am just interested in getting the upgrade GUID and the previous product GUIDs. I was able to locate the extracted .msi files on my hard drive. Thank you all for your help. -Original Message- From: Ch

Re: [WiX-users] Porting installer to WiX

They won't be able to say where it extracted because while different versions have had default locations, it's always been a setting the developer can override.  Short of searching the whole hard drive, the easist thing to do is enable MSI logging in the registry and start the install.   Once yo

Re: [WiX-users] How to add UI for Minor Patches(msp)?

On 7/16/2010 6:36 AM, Pally Sandher wrote: > The stock WiX UI's are found lacking when it comes to MSP support. > Fixed in v3.5, except for the WixUI_Advanced set. -- sig://boB http://joyofsetup.com/ -- This SF.net

Re: [WiX-users] Porting installer to WiX

On 7/15/2010 8:02 PM, Wilson, Phil wrote: > If you have WinZip and you open that exe with it, you may see the embedded > files. Or the internals might be proprietary. Otherwise as I said. If you run > the exe the MSI file will be extracted somewhere, just hunt for it and > copy/save it. > O

[WiX-users] Including referenced assemblies with a Project Output Group

I am using Wix 3.5 build 1909. I have some projects which include references to "third party" assemblies, ie not project references. Do any of the Project Output Groups settings cause these referenced assemblies to be included? Thanks Rob -

Re: [WiX-users] How to add UI for Minor Patches(msp)?

The stock WiX UI's are found lacking when it comes to MSP support. You'll find a lot of the text controls on certain dialogs e.g. ProgressDlg is conditioned with "AND NOT PATCH" so you end up with blank dialogs which you'll need to customize to fix anyway. I've never got around to fixing it myse

Re: [WiX-users] Embedded Chainer as Bootstrapper?

VC++ 2008 redistributables are available as merge modules in C:\Program Files (x86)\Common Files\Merge Modules\ Simply consume them in your MSI using Merge Elements. Unless you have other pre-requisites which don't supply merge modules e.g. .NET Framework then you shouldn't need any extra code.

[WiX-users] Embedded Chainer as Bootstrapper?

Hello, because I did not find information on this while searching I thought may be someone from the list has experience on this: For a product we need to ship e.g. the VC2008 redistributables as prerequisite and install it before our own product. This can be done with a Bootstrapper (setup.exe)

[WiX-users] Having different, localized msi files, and make VS bootstrapper determine the which one to call depending on OS-Language

Hi Our wix installer needs to be shipped in several languages. Using Wix localization, the output is one msi file for each language. To install various prerequisites (.NET framework, crystal reports, ... ) we use a bootstrapper that should then call the appropriate msi file depending on the

Re: [WiX-users] Best practice to include customer/user specific files (also when using a bootstrapper)

Hi I think your proposal would do. I also played around with the VS Bootstrapper and i find it does its job quite well. Having msi file not embedded in the bootstrapper is something I can live with. I probably stick to it if I find a way to call the different localized msi files, depending o

Re: [WiX-users] How to add UI for Minor Patches(msp)?

> MSP application uses the UI from the MSI it upgrades to. That's right. But it seems that the UI is used as ver1.0 not as ver1.1 with any changing in ver1.1 Now I investigate customize for show UIs which I hope instead of running ver 1.0 msi again. -

Re: [WiX-users] Retry at RMFilesInUse an invalid return value ?

CristianG wrote: > Just noticed that for RMFileInUse there is just OK. According to this blog post http://blogs.msdn.com/b/windows_installer_team/archive/2006/12/11/windows-installer-and-restart-manager-msi-files-in-use-v2.aspx MessageResult.Retry should be a legit return value. Is this a bug in

Re: [WiX-users] How to make Edit control readonly?

Too bad, the ScrollableText does not support dynamic text, so I cannot use it to show text defined in properties. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Scrollabletext-control-td708321.html#a708321 -- View this message in context: http://windows-installer-xml-wix-toolse