Hi,
I am also facing this type of problem.
Log file from canceling the product installation is as follows
MSI (s) (10:80) [07:34:58:368]: Doing action: ExtractFiles
Action ended 7:34:58: IsIISRunnig. Return value 1.
MSI (s) (10:C4) [07:34:58:432]: Invoking remote custom action. DLL:
C:\Windows\
Burn automatically finds external files for MsiPackages so a Payload under
an MsiPackage is *very* rare. ExePackages need Payload elements any time
there are supporting files for the ExePackage to bundle up so those are
more likely than MsiPackage Payload elements.
On Mon, Mar 18, 2013 at 6:02 PM
VS2012 Ultimate shipped with 130 packages.
On Mon, Mar 18, 2013 at 5:59 PM, Hoover, Jacob
wrote:
> Depending on your upgrade plans, you can have multiple files per
> component. If you are always doing major upgrades, this isn't a huge
> ordeal (though if any non-key file gets damaged y
Certainly an external CAB file or in the case of an Exe installer, whatever the
3rd party vendor deems needed to sit along-side the installer (Ini, Inf, Zip,
Cab, Dat, ...).
-Original Message-
From: Wheeler, Blaine (DSHS/DCS) [mailto:bwhee...@dshs.wa.gov]
Sent: Monday, March 18, 2013 7
Depending on your upgrade plans, you can have multiple files per
component. If you are always doing major upgrades, this isn't a huge ordeal
(though if any non-key file gets damaged you have to send custom parameters to
msiexec to force it to rewrite all the files). A second option woul
I was afraid you were going to say that, I am actually in the process of
trying to distribute components across features since reducing them is not
an option. What is the best practice in this scenario? The number of
components is rather large and this would result in a lot of registry
write operat
Why would you put a element under an or an ?
Payload seems redundant when it's the child of one of the other elements,
particularly if the MSIPackage has the cab embedded in the msi file.
Blaine Wheeler
Department of Social and Health Services
Project Coordinator
SEMS Operations
360.664.541
Its the Feature Component mapping. Reduce the number of Components to
succeed. You can also try to distrbute the Components across more Features
but that only works to a certain degree.
On Mon, Mar 18, 2013 at 3:42 PM, Chinnappa, Sarvesh [Audatex - Americas] <
sarvesh.chinna...@audatex.com> wrote
Hi,
I am facing an unusual problem with my installer. I will try explain in detail,
may be there is a workaround for this issue.
1. The installer is rather large >5GB with a lot of files, mostly data files
used by the application (a separate installer)
2. I am using heat to harvest the fi
Thanks a lot Rob, that did it
Bala
> From: r...@robmensching.com
> Date: Mon, 18 Mar 2013 14:38:11 -0700
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] XmlFile supports /parent::* Xpath syntax ?
>
> When using XPath advanced features, be sure to set the
> XmlFile/@SelectionLang
StevenOgilvie wrote
> As in previous email WIX has built in vars...
> \dev\myapp\bin\$(var.Configuration)\myapp.exe
>
> here is more info:
> http://wix.sourceforge.net/manual-wix3/votive_project_references.htm
For posterity, do I understand correctly that if you leave out the project
name from th
Thanks Rob, I am using older version, it did compile and generated msi but
when I uninstall, nothing removed. I see lots of debug msg from msi when I
tried to capture it.
I have thousands of file with around 400 components, I placed remove file
and remove folder tag inside each end tag of compone
I think that error 0x8007006e means the file could not be opened. My first
guess would be that either it's missing or it is not XML.
On Mon, Mar 18, 2013 at 9:29 AM, Sean Farrow
wrote:
> Hi all,
>
> I’m just refactoring and upgrading an installer from v2 to v3.8 of Wix.
> We are using an XmlCon
I know basically nothing about COM+ but a little detail about the exact
error codes you are hitting might help others.
On Mon, Mar 18, 2013 at 10:05 AM, DexterSinister wrote:
> Like the subject line says ...
>
> I'm using WiX v3.7.1224.0 to build an installation package for an app that
> has a
When using XPath advanced features, be sure to set the
XmlFile/@SelectionLanguage='XPath'. The default is 'XSLPattern' which
doesn't have many features of full blown XPath (but XSLPatter works with
older MSXML versions).
On Mon, Mar 18, 2013 at 11:31 AM, Bala K wrote:
>
> Hi am using trying to
Should work. What did the verbose log file tell you?
On Mon, Mar 18, 2013 at 11:21 AM, Ashish Naik wrote:
> Hi,
> Can some one pl provide example on removing folders using wix 2.0. I tried
> using remove files and remove folder but it doesn't work.
>
> Thanks
>
>
We've got a shell extension which hooks into Explorer.exe menus for our
stuff.
It installs ok using a WiX fragment I generated using heat.exe. But when I
try to upgrade it (major upgrade), the "files in use" dialog displays and
says that it must stop explorer.exe to update the files, and it giv
Hi am using trying to use util:XmlFile to change an xml file but it fails when
i use a specific XPath, saying it couldnt find the path.
ExecXmlFile: Error 0x80004005: failed to find node: //Name/parent::Application
in XML file: C:\Program Files\*\foobar.xml
I have tested my xpath query on onl
Hi,
Can some one pl provide example on removing folders using wix 2.0. I tried
using remove files and remove folder but it doesn't work.
Thanks
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppD
Like the subject line says ...
I'm using WiX v3.7.1224.0 to build an installation package for an app that
has a COM+ service
application ... I've tried to use the COM+ custom actions and have had
nothing but failures, this
installer & app were working until the app was updated to use .NET v4 - I
Hi all,
I’m just refactoring and upgrading an installer from v2 to v3.8 of Wix.
We are using an XmlConfig from the util extension to modify a config file that
is being installed with a .net application.
The file is being installed—looking at the directory as the product is being
installed, but I
Burn is a bootstrapper/chainer, it manages things at install time so I
don't think it'll help migrate your code. However, the related bundle
feature in Burn is pretty cool, especially for language pack scenarios.
Essentially, your main product installs as a Bundle (aka: uses Burn). Then
language pa
Rob, when you mention that "Burn adds a couple features (add-on related
bundles) that make doing language packs really sweet" could you explain a bit
more on that? What features does it add? We are just about to convert our
InstallShield Language pack projects to WiX, but we are also looking at
Hi,
I understand the benefits for some, we just advocate sim-ship of localization
and treat language resources like any other file, but then languages are our
thing.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 15 March 2013 15:53
To: General discussion for
Trying with a reply since I failed with my last post to get it accepted by
the mailinglist.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSI-differs-when-run-with-Burn-tp7584374p7584395.html
Sent from the wix-users mailing list archive at Nabble
25 matches
Mail list logo
