Maintec's Data Center Management services empowers companies to securely and
remotely
http://www.maintec.com/data-center-management.html
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive
It sounds like you are almost there, the trick is to use * as your component
guids then wix will get it right for you (shared components will use the same
guid as determined by the keypath).
http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou
rce-file/
I also use a
I have the same problem for our installer as well. I have now seen a custom
action reporting success in out own logging and then the see in the MSI log
that the CA fails.
A part of the log where it fails:
MSI (s) (A8:38) [13:37:49:868]: Invoking remote custom action. DLL:
Hello.
I spend a lot of time in attempt to make my C# BA to restart computer after
installation, but without any success. Native
'WixStandardBootstrapperApplication.RtfLicense' seems to work fine, and I
didn't find in Wix sources any reasons why it doesn't work with my BA. I'm
sure I missed
Having already done some research, it appears that single-MSI multi-language
installers are not supported by Windows Installer, and thus, not by WiX.
However, the latest information I could find that actually looked definitive
was from 2007, and I'm wondering if there has been any progress
You might be encountering this:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Two-Wierd-Inst
aller-Problems-DTF-and-QuietExec-td7220939.html
From: hansdegroot hans.degr...@nice.com
Sent: Tuesday, March 13, 2012 9:07 AM
To:
Hi Martin,
I too stumbled upon that sln, but was so green with WiX that I was unable to
follow the example.
Did you get anywhere with you solution?
Regards
Anthony
--
View this message in context:
The Windows Installer behavior has not changed. :(
On Tue, Mar 13, 2012 at 7:26 AM, Dave Mateer dave_mat...@ntm.org wrote:
Having already done some research, it appears that single-MSI
multi-language installers are not supported by Windows Installer, and thus,
not by WiX. However, the latest
They may not be supported but I've done it in InstallShield with and
without a Setup.EXE.
http://www.installsite.org/pages/en/msi/articles/embeddedlang/
The setup.exe with lanuage selection and command line passing to specify
the embedded language transform to use is the officially
If you really only want package name and shortcut localization, it may be
possible to do with a few conditions in an English MSI and some property
settings. See ARPCOMMENTS ProductName etc.
How will you determine what language to use, will it be passed in from your
bootstrapper or based on OS
Transforms are transforms - they apply to the MSI file, not just the UI. I've
changed Shortcut names, custom action conditions and (I'm pretty sure)
ProductName using transforms.
Phil W
-Original Message-
From: Dave Mateer [mailto:dave_mat...@ntm.org]
Sent: Tuesday, March 13, 2012
On 13-Mar-12 10:26, Dave Mateer wrote:
99.9% of the payload in my installer is the same between the various
languages.
The canonical way is to have one language-neutral installer and n
language-specific installers.
Is there any way to officially do this without duplicating the content? I
12 matches
Mail list logo
