RemotePayload was incorrectly allowed to be on MsiPackage and MspPackage. It is
possible in the fix that MsuPackage was removed. It probably shouldn't be. You
could open a bug to track the issue.
-Original Message-
From: Prajas John [mailto:prajas_j...@deepsea.com]
Sent: Friday,
Based on something Rob wrote at some point, I've been using * as Product Code
and not changing the upgrade code.
It really seems like the OP's basic requirement is that each release is an
independent product, so if they just do that they'll be 99% of the way there.
Of course the last 1% is
Finally resolved this issue when I have following on the Display.Embedded
mode of my BootstrapperApplication:
1. Add handlers for DetectComplete, PlanComplete and ApplyComplete. Call
Engine.Detect().
2. Handler for DetectComplete calls Engine.Plan(Command.Action).
3. Handler for PlanComplete calls
Following up, the tutorial, when running, should show the dialog, however
it doesn't:
this.Core.CreateWixSimpleReferenceRow(sourceLineNumber, CustomAction,
ShowMessageImmediate);
What am I missing?
Eric Stott
(623) 261-7208
http://stottcreations.com
http://biztalk.stottcreations.com
well I guess I don't think this is a bug...
However I did fix the issue.
1. took '.' out of my progress text strings
2. changed balextension DLL (WixStandardBootstrapperApplication.cpp) in
method:
OnExecuteMsiMessage
from:
ThemeSetTextControl(m_pTheme,
I have a bundle with an mba and several nearly identical MsiPackages (which
install various printer drivers). So except for a different path to the msi
the bundle MsiPackage authoring is identical for each driver package. The
thing that I noticed is that when I set LOGVERBOSE on the command line
The upgrade path wouldn't concern me to much, because our end customer
relationships are all 1-to-1. But you got me thinking with the signature part.
Maybe my approach on this was not quite the best. Maybe I should consider just
teaching my internal customer's how to make easy setup projects
7 matches
Mail list logo
