All true. We assembly a Zip file for consumption as a plugin by one of our
applications. The files in the Zip file are explicitly NOT tracked. They are
only deployed into temporary folders which are purged on install or upgrade.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack
On May 15, 2014 3:14 PM, Pavan Konduru wrote:
It's usually best not to include zip files as the installer treats it as a
single entity.
When you blow up the contents of the zip file through custom actions, the
installer cannot track those contents as part of upgrade/uninstall/patch.
--Pavan
--
It's usually best not to include zip files as the installer treats it as a
single entity.
When you blow up the contents of the zip file through custom actions, the
installer cannot track those contents as part of upgrade/uninstall/patch.
--Pavan
-Original Message-
From: John Cooper [mai
We use DotNetZip. There's a NuGet package for it, and writing a C# CA from it
to do what you want is pretty easy.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenr
Are there any existing custom actions that can compress a directory or list
of files into a zip? I need this because part of the install payload is an
'App Package', this is a '.app' file which is just a zip with alternate
extension. I need to modify an XML file which is the 'manifest' for this
'Ap
Hi Tim,
Please see (much further) below an implementation I use.
It will turn this:
Into:
And on uninstall will remove the bits it has created.
Most of the time I
It works for all of them... Read this again...
http://blogs.technet.com/b/alexshev/archive/2009/05/27/from-msi-to-wix-part-25-installable-items-updating-xml-files-using-xmlfile.aspx
Carter
Quoting TimM :
> Okay still having an issue with util:XmlConfig. If I use the following:
> Guid="{68FCE72
Okay still having an issue with util:XmlConfig. If I use the following:
Then the install will work and no errors, the .config file will look like
the following:
As you can see the ClientMode is in the wrong location, it should look like
this:
Hello WiX users :)
Has anyone had any success running any of the WiX command line tools under
the Mono framework?
What I am trying to do is perform an administrative install of the product,
digitially sign everything, and then repackage it and sign the MSI from a
secure, readonly linux liveCD.
I
unsubscribe
-Original Message-
From: Alasdair King [mailto:alasdairk...@gmail.com]
Sent: Thursday, May 15, 2014 5:08 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] WixBundleInstalled in Managed Bootstrapper Application
OK, done some testing:
* WixBundleInstall
There is a bug open on this: http://wixtoolset.org/issues/3640/
You can usually work around this by using subfolders, like setting the
Exepackage Name="Exepackage1\Setup.exe".
On Thu, May 15, 2014 at 9:47 AM, Valentine Vinogradov
wrote:
> Hello! Are there any possibilities to prevent taking loc
Hello! Are there any possibilities to prevent taking local files with the
same name laying in download folder for the package expected to be
downloaded?
For example, if I have Exepackage Name="Setup.exe" with download url and
remotepayload, it tries to take file setup.exe in the execute folder and
OK, done some testing:
* WixBundleInstalled does indeed report the installed state of the bundle,
before and after DetectBegin.
* A bundle can indeed install zero MSI packages and be installed. The
installation state of the bundle is independent of the installation state
of the MSIs contained wit
13 matches
Mail list logo
