My apologies again! It was a dumb typo on my part. As I was pasting an
example of my code into the editor to post here, I realized that the last
parameter of WcaAddTempRecord should be a ComponentId, and I had used the Id
of my custom xml element. Changing that parameter to the Id of the
I am looking for advice on how to sort out a problem I having using
WcaAddTempRecord. My immediate CA creates a BYTE array (an encrypted
'blob') which I need to write to the Registry as a REG_BINARY type value. I
am trying to use WcaAddTempRecord to the Registry table, ( using the code in
wix
See these blog posts. Both of these have a note about progress on 3.10
https://www.firegiant.com/blog/2015/6/2/wix-online-meeting-68-highlights/
https://www.firegiant.com/blog/2015/6/16/wix-online-meeting-70-highlights/
On 22 June 2015 at 17:55, Rob Mensching r...@firegiant.com wrote:
PS: WiX
While doing other research I came across these threads, and made note of them
in the event that I might need them in the future. They might be helpful to
you:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Resume-Installation-Plan-td7579146.html
Thank you, Phil.
Unfortunately, I only have one MSI that installs both my application and
ext2fsd.
Are you suggesting that I split them up into two MSIs and then bundle them
using Burn?
Thank you.
--
View this message in context:
I guess I misread your question and assumed that you were using Burn. Given
that I came across those posts I thought they might be helpful but if you
are not using Burn I can't really make any suggestion.
I have only used the approach of putting each app and each driver in a
separate UI-less MSI
I'm trying to implement same version upgrades in our bootstrapper. We build
our product in one build process and later create the installers in a
second package process. This allows us to repackage our product when fixing
installer changes that do not affect the product in any other way. We do
not
Any BA can choose to allow same version upgrades. The wixstdba does not.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: Edwin Castro [mailto:egca...@gmail.com]
Sent:
Not today. Creating the same bundle with the same version just isn't something
wixstdba considers a real scenario today.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
Conversely, is there a way to DISALLOW same version upgrades in bundles
using wixstdba?
I'm trying to figure out what my options are.
On Tue, Jun 23, 2015 at 2:32 PM, Rob Mensching r...@firegiant.com wrote:
Any BA can choose to allow same version upgrades. The wixstdba does not.
My ExePackage gets uninstalled during upgrades and I'd like to only
uninstall during an actual uninstall. Any suggestions on how I might go
about doing this? I was hoping I could do something in my bafunctions.dll
but I'm hitting a wall in my brainstorming.
My bundle consists of the following:
*
Give it a Provides element from Dependency Extension to enable reference
tracking.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Edwin Castro
12 matches
Mail list logo