Windows installer looks at each item in a patch and repairs the entire feature
that item belongs to (unless that feature wasn't installed). Thus, if the new
item is in an already existing feature, and that entire feature isn't in the
patch itself, then Windows Installer may have to prompt for so
I'm still curious what the update log would have said WRT the RegisterProduct
action. Can you reproduce this issue?
> From: dsaw...@box.com
> Date: Wed, 7 Aug 2013 20:47:47 -0700
> Subject: RE: Installation failed, but product updated
> To: wix-users@lists.sourceforge.net
> CC: os...@live.com
>
Hi Blair,
Thanks for the great tip! My action is scheduled as:
REMOVE="ALL"
I can change it to After="RemoveFolders". I'm still surprised the new
files did not get installed but the product got registered. I would expect
either both or neither.
I think the reason the custom action was scheduled
I'm creating a patch using WiX's native support: admin install of both
packages, compile wxs with candle, link into .wixmsp with
light, create transform between .msi's with torch outputting a
.wixmst, and put it all together with pyro.
What's the best/correct way to add a new registry key in the
Yup pretty easy
i.e. MyBundle.exe APROPERTY=DIFFERENTVALUE
Bundle.wxs
Then in MSIPackage element:
In your MSI
If you don't use the command line parameter the default value that you set i.e.
Value="DEFAULTVALUE" will be used :)
Steve
-Original Message-
From: Ian Williams [mailto:
Using WixStdBA with WiX 3.6.
Is there a way allow custom command line parameters to set values of Variables
in the bundle?
Thanks,
Ian
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free trouble
The MSI is written by a third party and it is explicitly written to only setup
the service if the MSI is installed per-machine. When the MSI is installed
per-user, it suppresses the "setup" and "launch" service steps (probably
because there is no elevation available). They also wrote it such tha
You have multiple entries in the control panel because you are not deleting the
older versions that you are possibly overwriting by installing your newer
version.
Delete the older versions and they will go away from the control panel, leaving
just the newest version.
> From: chaita...@pointc
Hello,
I'm having trouble getting my managed custom UI to be loaded by burn. The
key error in the log seems to be:
Error 0x80131902: Failed to create the managed bootstrapper application.
>From research, it seems that this is a very general failure. The usual
problem that seems to cause it is
That Windows Installer decides on "Feature level" which files to touch rather
than on "Component level" explains a lot, as I had used only a single
feature. After dividing this feature into >100 smaller features the patch is
ready after 18 minutes. That's still not great but a significant improveme
Mission accomplished! thanks for the assistance.
Phill
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Unspecified-Error-after-signing-bundle-tp7587845p7587864.html
Sent from the wix-users mailing list archive at Nabble.com.
-
Even better would be to get the MSI fixed. Sounds like there are a couple
issues there. Everything should "Just Work" without forcing anything.
On Wed, Aug 7, 2013 at 2:10 AM, Hendryk Irmischer wrote:
> Yep, ForcePerMachine="yes" did the trick.
>
> First I tried to copy the missing CustomActions
I just read the doc for Insignia more carefully and I think I see what I am
doing wrong. I had originally not used insignia because it seemed to be
needed for signing 'external CABs' and I am not using an external CAB. But
I now see how it is use to extract the engine.exe from a bundle. I will
w
I'm sorry, I do not quite understand what you mean by 'provided targets'. I
used the following command in the Post Build event for the bundle project:
(The certificate was previously imported into a local catalog. This is the
same command that I also use in the Post Build event for my MSI proje
And off course after a long day of searching and trying, just when I posted my
question I find the solution to this problem:
I had:
ElementPath="/configuration/connectionStrings/
add[\[]@name='MyConnectionString'[\]]"
on two lines. After making it more readable to post it in my question it
s
By using that it will delete the older version..i should not delete the older
versions..
by using these commands it will not delete the older version..Newer will update.
From: santhosh yalamuri [santhu@gmail.com]
Sent: 07 August 2013 17:21:39
T
Follow the steps given in this link :
http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/
Thanks,
Santhosh
On Wed, Aug 7, 2013 at 3:12 PM, Chaitanya Sanapala [PC-BLR-DEV] <
chaita...@pointcross.com> wrote:
> Hi,
>
> Iam Using Major Upgrade For my installation.the files are
Hi,
I'm creating a setup for a webapplication. I used the method described here
(http://www.paraesthesia.com/archive/2010/07/30/how-to-consume-msdeploy-staged-web-site-output-in-a.aspx
) to get the right files for my webapplication. It all works great.
Now I want to make some changes in the Web
Hi,
Iam Using Major Upgrade For my installation.the files are updating
successfully..
But in my control panel it is showing Multiple entries...
How to Update the control panel entry.???
I'am maintaining the same Upgrade code for base & upgrade installers.
Different Products Codes.
How to solve th
Yep, ForcePerMachine="yes" did the trick.
First I tried to copy the missing CustomActions from InstallExecuteSequence to
AdminExecuteSequence. This worked too for me, but your solution is clearly the
better one.
Many thanks for the fast response.
Greetings
Looking inside of
20 matches
Mail list logo
