* UserLanguageID - gets the language ID for the current user locale.
* WixStdBALanguageId - gets the language in effect for the WixStdBA user
interface.
When would these have different values? I’m wondering if, since
WixStdBALanguageId is new in v3.10, can I use UserLanguageID with v3.9
Now we KNOW we have found the -real- problem... :)~
Tried to use Upgrade to detect when a reboot is required:
Upgrade Id=$(var.UpgradeCode)
UpgradeVersion Minimum=$(var.BGProductVersion)
IncludeMinimum=no
OnlyDetect=yes
Every decent installer comes with command line arguments documentation.
You should ask the supplier or browse their web site for command line
options for silent install / repair / uninstall. It really shouldn't matter
if it was packaged with WinZip or any other tool.
The harder bit is usually
I'd like to install or uninstall an ExePackage whenever an MsiPackage is
selected for install or uninstall.
Details:
* ExePackage must be installed whenever MsiPackage is selected for install.
* ExePackage must be installed before MsiPackage is installed.
* ExePackage must be uninstalled whenever
OnDetectComplete handler is safe.
OnDetectBegin if you know that WixStdBALanguageId has been initialized prior
to OnDetectBegin.
--
View this message in context:
Thank you for the information regarding en-US strings.
Might you know any solution how to use the kazakh language, as all I do is copy
paste WixUI_kk-KZ from Wix source files?
Best Regards,Gasper
Date: Wed, 1 Apr 2015 12:53:00 -0700
From: nir@panel-sw.com
To:
Think we found the real problem
[2D80:2FB8][2015-04-02T12:28:40]i103: Detected related package:
{DCB7DC05-888D-4B9B-904B-EA1DB739C994}, scope: PerMachine, version: 6.4.0.171,
language: 1033 operation: Downgrade
[2D80:2FB8][2015-04-02T12:28:40]i103: Detected related package:
I guess the only issue is that when you extract their package, that in addition
to the setup.exe file, there are 35 folders and 208 supporting files. I believe
I misspoke when I said that I could use Burn to repackage this into a single
file (because I would just run into the same issue I have
What did you copy and past them into?
A wxl file has an header that specifies the code page. If you also create
string entries for the Codepage, you can then use the wxl string entries to
set the Product/@Language=!(loc.LCID) and the
Package/@SummaryCodepage=!(loc.SummaryCodepage). Something
I'd consider shipping the setup.exe (and any support files) in the bundle
without the archive wrapper.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: maverick02 maverick02
Thank you Rob for the quick reply. Just to be clear, this package that I am
bundling is not mine, but is provided by a 3rd party. It is also quite large
(at about 70 MB) and so it would be nice if it would download only on demand
when its not yet already installed. Are my options essentially:
Hi Everyone,
I am looking for some guidance on doing the following. I want to bundle a
prerequisite package that can be downloaded from a url at install time. The
problem is that this package comes as a self-extracting Winzip archive and if
the installation is to be silent, I need to do it in
1) Our MSI sometimes requires a reboot after certain upgrades. We have
programmed ScheduleReboot with the necessary condition. The previous version
is removed and reboot is requested when run directly from the MSI.
a) No reboot is requested when run from the encompassing bundle. The MSI log
It works in OnDetectComplete!!! Thanks everyone for all the help. One
question though:
In my HyperlinkSidebarTheme wxl's, I use [WixBundleName] in several strings
(Caption, Title). If I use one of those strings in value of Window in my
HyperlinkSidebarTheme.xml, what is shown at install
Not the best choice by the 3rd party vendor, but you can work around it with an
exe pakage with multiple Payload elements inside...
ExePackage ...
Payload .../
Payload .../
Payload .../
All 208 of them...
/ExePackage
Just keep the relative paths the same as what
Or just download and extract their self-extracting installer, extract it, and
place it on a web server you control (no need to bundle it). Then in your
bundle you just reference that payload. You're still going to have to update
your bundle when you decide to release/approve an updated
Maybe then what I can do is download their package, extract it, and create a
separate Burn project to package, build and upload it to a server I control.
The only downside is I would have to manually redo this whenever the 3rd party
releases an updated package.
- Original Message -
If you're writing code to deal with this, can't you compare the
installed version (ProductCode, ProductVersion) with the download
version and skip the download? I'm assuming you may know some of this
in advance, and that they don't change the version at the download
location too often or you'll
I would let Burn do all the downloading but if you can't just create process
the package, then you'll have to write something that can be create processed
then do the multiple steps.
For example, how would Burn know what to do here? It's all custom... which
basically comes down to Don't do
Is there such a thing as m_pEngine-GetVariableString, and can it be used to
get Bundle Variable values in BAFunctions.dll? If so, what is the syntax?
Thanks very much!
David
--
Dive into the World of Parallel Programming
It occurs to me that I don't want to change the ExePackage's request state.
Rather I want to change it's action state to the same action state selected
for the MsiPackage.
Is there a way to get and set package action state?
On Thu, Apr 2, 2015 at 2:14 PM, Edwin Castro egca...@gmail.com wrote:
21 matches
Mail list logo
