In my experience, that message shows up if your exe returns an error and
doesn't have an application manifest. Add a manifest to the bootstrapper exe
(specifically one that includes the aseemblyidentity and
requestedexecutionlevel tags) and you shouldn't see that second message anymore.
-Ari
You might need to get the latest WDK from Microsoft, which ships with the
DIFxApp.wixlib. It's possible that WiX isn't including the most recent DIFxApp
redist. We do our builds with the wixlib from the WDK and not what comes with
WiX, just in case the WDK has something newer. You might try t
In WI 4.5, you don't need a bootstrapper. You do need to write a chainer exe,
but WI 4.5 lets you put that exe into the binary table of your "main" MSI. I
still think it's significantly easier to just write a bootstrapper that does
the chaining instead of writing a bootstrapper to upgrade to W
l search for one - I don't doubt what you are
saying only need this to be filed in a proper way.
Best regards,
Calin
- Original Message -
From: "Moradi, Ari"
To: "General discussion for Windows Installer XML toolset."
Sent: Thursday, March 05, 2009 4:5
Windows Installer will always keep a copy of your MSI file in
%WINDIR%\Installer. It needs it there to repair and uninstall the MSI. The
copy it keeps has any embedded cabs removed. But I seem to remember that it
copies the entire MSI file to the Installer folder, then removes the embedded
c
I found the exact same problem and (after a lot of investigating) found that on
my machine, it was PSPad causing the problems. Every time I launched PSPad
(ran the app, not install it), it was attempting to reregister vbscript.dll.
Since it runs unelevated, vbscript gets registered in my user
Take a look at MsiGetFeatureCost --
http://msdn.microsoft.com/en-us/library/aa370115(VS.85).aspx
As long as you've opened the package and called MsiDoAction on the 3 actions
you've mentioned, it works well.
I think MsiEnumComponentCosts works too, but I find that getting the size of an
entire
$(env.TEMP) would give you the environment variable's value on the build
machine, which doesn't help at install time. So this doesn't really solve the
problem of finding the environment variable's value on the user's system. It
also still gives the value of the environment variable as it is se
It sounds like your component GUIDs changed between releases. Make sure all
the GUIDs stay the same.
And check the verbose log during the upgrade, it will tell you what it intends
to do with each component, which can help you figure out why it's doing that.
-Ari
-Original Message-
Fr
I'm pretty sure that the Windows Installer uses CreateProcess internally to
execute type 50 custom actions. So, it will always execute the new process at
the same level as the Windows Installer process. If it's running out of the UI
sequence, that means that it won't be elevated and will fail.
I think a LaunchCondition with the property Msix64 will do what you want.
-Ari
-Original Message-
From: Jeremy Lew [mailto:j...@liquidmachines.com]
Sent: Monday, January 26, 2009 2:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Prevent 32 bit MSI in
10:23 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixDIFxAppExtension and MergeModules
Moradi, Ari wrote:
> There isn't a DIFxApp merge module in WiX, but there is one in the WDK. WiX
> can certainly add a dependency on a merge module that
ller XML toolset.
Subject: Re: [WiX-users] WixDIFxAppExtension and MergeModules
For redisting to other... probably. Unless everyone is using the WiX toolset.
-Original Message-
From: Moradi, Ari [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2008 15:05
To: General discussio
components directly to your own merge
module, right?
-Ari
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2008 5:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixDIFxAppExtension and MergeModules
Mo
on those rows where the merge conflicts happen?
Hmm.
-----Original Message-
From: Moradi, Ari [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 11:59
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixDIFxAppExtension and MergeModules
Mergemod.dll
[WiX-users] WixDIFxAppExtension and MergeModules
If the rows are duplicate, I thought mergemod.dll would let them through. Is
it more accurate to say that the DIFxApp actions Id's have been modularized and
that is colliding?
Can you maybe share out a merge.log that shows the merge problems
Hi folks,
I'm having a problem with the WixDIFxAppExtension when I'm using it in merge
modules, and I'm wondering if someone can offer me a simpler workaround than
what I'm currently planning on doing :)
The problem is caused when we try to build two different merge modules using
WIX (v3.0.462
Hi,
Our team uses doxygen to create html documentation for our C++ source, and it
works really well. I'm just curious if anyone out there is aware of a similar
tool that will generate documentation from wxs files.
I'd like to be able to put comments in some format in each wxs file and then
ha
18 matches
Mail list logo
