[WiX-users] (no subject)

-- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlc

Re: [WiX-users] Chaining MSIs together

The MSI teams discourages "nested" aka "concurrent" installs. MSI chaining is relatively new and requires MSI 4.5 which frequently requires a bootstrapper to get you to that level ( i.e. MSI 2 / 3.1 not enough ). There terms "bootstrapper" and "chainer" are used interchangeably but there is a s

[WiX-users] (no subject)

Sent from my HTC on the Now Network from Sprint! -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation t

Re: [WiX-users] Chaining MSIs together

A bootstrapper is an executable that is responsible for running other setup programs (.exe) and MSI packages in the order required by the product getting installed. An example would be the Visual Studio installer. It provides a user interface that determines what MSI products need to be installe

Re: [WiX-users] Chaining MSIs together

A bootstrapper is going to be an executable file that contains a "package" of your different installers. I'm currently using NSIS for a bootstrapper while burn is under development. It won't be a single MSI, but rather an executable. Microsoft Installer supports chaining of .MSIs together as of

Re: [WiX-users] Chaining MSIs together

So, dotNetInstaller is a package of .NET classes that facilitate chaining together MSIs? But, if it requires .NET then wouldn't any bootstrapper one builds with dotNetInstaller require that it be bootstrapped itself with .NET? My target computers don't necessarily have the .NET runtime installed.

Re: [WiX-users] Chaining MSIs together

Burn is meant to provide this functionality, but it is under developed. There are plenty of chaining/bootstrapping products out there in the meantime. One I like is DotNetInstaller: http://dotnetinstaller.codeplex.com/ . You could use this to install the prerequisite Adobe AIR, if necessary,

Re: [WiX-users] Problem with quotes in CustomAction

Hello Kevin I have been able to do a similar thing with no problem. I expand out the command arguments using custom actions and then pass one property through to the ExecCommand This does allow you to see what is happening quite well in the log. My approach:

Re: [WiX-users] Suppress Feature selection in patch

No, nothing fancy. Just following the http://wix.sourceforge.net/manual-wix3/patch_building.htm. The installers are pretty much the same, just did one line of code change to have a difference. Features are all the same. Any other ideas? I'm using 3.5.2519 -Original Message- From: Pally San

[WiX-users] Problem with quotes in CustomAction

I seem to have hit a bug with quotes in CustomAction. Note the variations below. Either of these should work. However, when the command line parameters are expanded out the [MYDIR2] path winds up with no quote in front of it, which presumably causes the call to the executable to fail. I

[WiX-users] Chaining MSIs together

Hello, I have an existing installer that I wrote in NSIS that does several things. It installs the Adobe AIR runtime by invoking an executable provided by Adobe. It then installs our AIR application, again using installation utilities provided by Adobe. And finally, it installs media which our AIR

Re: [WiX-users] Creating Patch

Thanks, i just had the wrong file... :-( That worked well -Ursprüngliche Nachricht- Von: Pally Sandher [mailto:pally.sand...@iesve.com] Gesendet: Donnerstag, 12. Mai 2011 12:46 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] Creating Patch You can't

Re: [WiX-users] Ignoring config files with patch

Are the config files being included in the patch? Patchwiz log should tell you what exactly what it is choosing to include. If so it's overwriting them with what it thinks are newer files which is what I suspect is the case as Windows Installer won't overwrite updated files with older ones in m

Re: [WiX-users] Suppress Feature selection in patch

Using WiXUI in WiX 3.5 it should go from WelcomeDlg directly to VerifyReadyDlg when applying a patch. Have you customized the WiXUI or written your own UI? Palbinder Sandher  Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate +

Re: [WiX-users] Patch and searching for date

Yes that's how patching works certainly using the patchwiz method which from your other message is what you're attempting. PatchWiz method creates a patch using a base package & an updated package. Only what has been changed between the base package & updated package is included. Note it's meth

Re: [WiX-users] Creating Patch

You can't use Votive to build patches as there's no "patch" project type (or there wasn't last time I checked) which is why Visual Studio is erroring. Post your patch.wxs & the commands you're running which give you that error as the error & information you pasted is too vague to diagnose. I've

[WiX-users] Creating Patch

Hi, i know i have a lot of questions. I am just new in wix. I try to create a patch in wix. For this purpose I use the following page: http://wix.sourceforge.net/manual-wix3/patch_building.htm. When I use light.exe application, the error: lght0093: cout not find entry section in provided list of

Re: [WiX-users] Testing the UI

With settings affecting the layout I primarily mean settings affecting the fonts. Play with things like Windows XP: Use large fonts Windows 7: DPI settings Control Panel\Appearance and Personalization\Display -> use larger here 2011/5/11 Francisco Gabriel Malbrán : > Thanks Tobias. This is most