No, but Rob Mensching himself wrote Well there is the bug then. as an
answer of my question.
Because of that I thought that it will be fixed.
-Ursprüngliche Nachricht-
From: Nicolás Alvarez
Sent: Saturday, November 30, 2013 6:10 PM
To: General discussion about the WiX toolset.
Subject:
how did you load your BA?
Date: Fri, 29 Nov 2013 11:07:37 +0530
From: dileep.sanamp...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] [WIX]: How to trigger my MSI file when I select
install option in Wix Custom Bootstrapper UI
Hi Blair,
Thank you for the
Only via using the technique documented here:
http://wixtoolset.org/documentation/manual/v3/msbuild/daily_builds.html
From: steven.ogil...@titus.com
To: wix-users@lists.sourceforge.net
Date: Thu, 28 Nov 2013 16:48:26 +
Subject: Re: [WiX-users] WiX v3.8 released! [P]
Classification:
alternately:
http://wixtoolset.org/documentation/manual/v3/msbuild/daily_builds.html
Date: Fri, 29 Nov 2013 14:25:22 +1100
From: goodridge@gmail.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Cannot create patch using 3.7/3.8 when original MSI
built with 3.5
When Burn installs a newer MSI that MSI should still generally remove older
versions of itself (#1 reason: your customers may not do what you expect).
Having said that, if an MSI does what is expected, then the older MSI will be
removed as part of its upgrade. When the older bundle is then
Do msiBlock and msiOld share the same ProductCode?
Is that ProductCode (or any ProductCode) also shared by msiNew?
Do all three share the same UpgradeCode?
Does msiOld have any code to guard against it being the source of a downgrade?
From: i...@tobias-erichsen.de
To:
Bugs discussed on these lists remain on these lists unless tracked, and the
only way it will be tracked is if someone enters the bug into the tracking
system. The best person to enter an issue into the tracking system is the
person that discovers the bug, not necessarily the person who
msiOld: productIdA, upgradeIdA
msiNew: productIdB (*), upgradeIdB
msiBlock: productIdA, upgradeIdC
The problem is that msiOld does not have any guard and that is why
I want to install some kind of (invisible) blocking-installer.
I cannot change the msiOld (because it is out in the open), but
I
Yeah, but I am massively randomized and can often lose things. If an issue is
important to you, it's very important for you to follow up on it. Email is
particularly lossy. Nicolas's suggestion to ensure a bug is open (you might
need to open it yourself) is a *very* good idea.
For the same
If msiOld has no guard at all, then it will potentially install itself on top
of anything, no matter what you do. All you can do is reduce its vectors of
installation.
If someone presents your msiOld via MSI double-click, you can prevent its
installation by having another MSI with the same
Hi All,
I have created a .msi installer using WIX. When i execute the installer
through command line it installs the application without any error
messages but when it i do it through clicking the setup that gets
created: MyWebSetup.msi, i am getting the below error message. There is
no error
Hi Blair,
I have created the C++ custom action project.
Created Dialog Resource file.
Created functions in C++ custom action DLL Main() to load the resource.
Build C++ custom action project.
Then, Added custom action dll into Bundle.wxs file.
BootstrapperApplication Id =MyCustomBootStrapperID
I was referring to the code in SampleDLL.dll. I assume you are not creating
your UI in DllMain(). There is a method that you export where your UI is
created that Burn calls.
Date: Mon, 2 Dec 2013 12:59:01 +0530
From: dileep.sanamp...@gmail.com
To: wix-users@lists.sourceforge.net
Subject:
13 matches
Mail list logo
