Hello Wix users!
I am trying to create a signed bootstrapper. I found that I need to also
sign the engine that is in the bootstrapper. I am using command line to
build the installer (so no wixproj).
I followed the steps I found in the documentation, but I still cannot
inscribe the engine
I recently filed bug 4448, in which the following response was posted:
Versioned companion files are atypical and would seem to bring their
own problems for upgrades and patching. We don't plan to expand *
GUIDs to cover this case.
That bug is probably not the right place to ask
Dear wix-users,
I have an wixproj producing an MSI for some Product A which contains some
Feature X that depends on some other Product B. Feature X is optional. I
don't want to add a Requires element to the Product element of Product
A as this will always create a dependency even if Feature X is
Thank you very much!
It is working like a charm. (Besides this weird property-naming.
SourceFile is not the source of the payload at runtime, but
name-property is the source. Who implemented that?)
Am 18.06.2014 14:13, schrieb Markus Wehrle:
Hi,
to place a package on disk layout you can use
Hi,
I used different installer (InstallJammer) to install my application. I have
now msi installer for the same application. Could you please tell me how I can
uninstall previous installation since I find no upgrade code in installjammer?
Or, is it only possible to update if the previous
The update behavior of msiexec and the UpdateCode property are specific to
MSI based technology. It would not know about other technologies like
InstallJammer.
--
View this message in context:
It sounds like the mba has a dependency file which should be added to the
bundle as a Payload element.
http://blogs.msdn.com/b/suzcook/archive/2003/05/29/debugging-assembly-loading-failures.aspx
Generally I would not test a setup on my development machine. No telling
what damage could be done.
What was the previous installer?
On Fri, Jun 20, 2014 at 9:32 AM, Phill Hogland phogl...@rimage.com wrote:
The update behavior of msiexec and the UpdateCode property are specific to
MSI based technology. It would not know about other technologies like
InstallJammer.
--
View this
Previous installer was InstallJammer. So, what would be the best solution for
this? Should I call uninstaller of the previous installation in
InstallExecuteSequence ? Any example for this?
Date: Fri, 20 Jun 2014 10:30:11 -0500
From: jeremi...@gmail.com
To: wix-users@lists.sourceforge.net
I'm no expert, but I do know that Windows Installer doesn't seem to use the 4th
digit in versions for much, so is it possible that the fact you only changed it
is simply confusing the matter? (I.e., violating expectations somehow so the
behaviour isn't right.)
Keith Douglas
Programmer
*Bump.* Anyone?
-Original Message-
From: George Fleming [mailto:gef...@microsoft.com]
Sent: Wednesday, June 18, 2014 12:35 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Applying two patches causes version number confusion
Our patches are cumulative, and uninstall is
I'll be uploading the triage meetings to YouTube soon
(https://www.youtube.com/channel/UCVJeW1mjSujNPfsCQhsg7qQ) where we discuss
this issue.
It came down to the fact that what you are doing is very unusual. Since it's so
unusual, you should manage the GUID manually. It certainly isn't a
SourceFile is consistently used throughout the WiX toolset as the location
to the source on your build machine where the bits that need to be included in
the resulting package need to be found. IIRC, the only place where
SourceFile is not used to mean a build machine path is on the File
I've seen this done by having the upgrade get the uninstall string
from the registry, where there should be a command you can use since
it's not MSI-based. Whether you should call it in the UI sequence or
the execute sequence or both depends on your requirements for silent
installs, meaning that
Hello, I am trying to recompile my installer. Below is the error I am getting,
but, I do not know why. I've read this can be caused by an already existing
registry key in the dictionary?
Error:
light.exe : error LGHT0001 : Item has already been added. Key in dictionary: 're
Could you post a copy of both of your Patch WXS files?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Applying-two-patches-causes-version-number-confusion-tp7595340p7595395.html
Sent from the wix-users mailing list archive at Nabble.com.
Sorry, I misunderstood as I am not familiar with InstallerJammer.
I did find this though.
http://stackoverflow.com/questions/14334012/how-can-perform-a-silent-uninstall-with-installjammer
Again, I'm not familiar with InstallerJammer and I'm assuming it doesn't
use WindowsInstaller???
Since
**If it uses windows installer that is**
Since you can have only have one install/uninstall at one time on a windows
machine this might not work if you try to uninstall during your new install.
On Fri, Jun 20, 2014 at 2:41 PM, Jeremiahf jeremi...@gmail.com wrote:
Sorry, I misunderstood as
I will give it a try and come back if it doesn't work.
Thanks a lot.
Date: Fri, 20 Jun 2014 14:41:06 -0500
From: jeremi...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Unable to uninstall previously installed product
Sorry, I misunderstood as I am not familiar
19 matches
Mail list logo
