Use heat http://wix.sourceforge.net/manual-wix3/heat.htm to harvest
your registration information and create a wix fragment that you can
include or copy/paste from...
It's actually very easy :)
-Original Message-
From: Brad Lemings [mailto:b...@rebit.com]
Sent: 20 June 2011 17:27
To:
To the OP, why doesn't your organization just download the source and
build the binaries themselves? That will solve the integrity validation
of all software used in the build process requirement. They can even
sign the exes with their own certs. Open source FTW :)
-Original Message-
As has already been said, if you really want to do this you must use Windows
Installer 4.5 and its multiple package installation chaining feature:
http://msdn.microsoft.com/en-us/library/bb736322(v=vs.85).aspx
InstallShield uses a bootstrapper. It can't magically extend the Windows
Installer
Not sure but have you tried it in the same format as
Package/@InstallerVersion:
http://wix.sourceforge.net/manual-wix3/wix_xsd_package.htm
So for 3.1, use 301. Etc...
Don't know about your second question.
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: 24 March
Do the files you're trying to create in your command already exist on
this PC? That would make the create database command fail.
Or are you saying that even on the same PC, the same command with the
same paths works in SSMS but fails in your MSI? Forgive me if you've
already covered this.
Set the ExeCommand attribute of your LaunchApplication CustomAction:
CustomAction FileKey=Connect.exe Id=LaunchApplication
Return=asyncNoWait Impersonate=yes ExeCommand=-demo /
-Original Message-
From: Michael Tissington [mailto:michael_tissing...@ciqual.com]
Sent: 04 March 2011 11:03
If you're sure there's a bug, you can file it on the bug tracker on
sourceforge.
But there's no bug here. You simply need to use double-backslashes in
the right way (no square-brackets). So your XmlFile node should look
like:
util:XmlFile Id=FileChange
though because I thought we'd tested this.
No matter, you've gotten to the bottom of it so again, thank you.
Regards
Jamie
-Original Message-
From: Thom Leigh
Sent: Wednesday, February 09, 2011 9:34 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users
I think you just include Properties in square brackets to use them? So:
File ... Name='[WIXUI_SYSTEMSHORTNAME].SSIS.dtproj' ... /
But that seems too easy so I'm probably wrong!
-Original Message-
From: Jamie Thomson [mailto:ja...@jamie-thomson.net]
Sent: 07 February 2011 16:29
To:
Your error sounds like an encoding bug. The error says '' is undefined.
'' is the UTF-8 BOM (Byte Order Mark). I expect your .js file is being saved
as Unicode with Byte Order Mark, when it should be being saved as ANSI (or as
Unicode but without BOM)
-Original Message-
From:
Does the msi exist in any of the cabs or setup.exe file? (try opening
them with 7zip) What version of InstallShield was used to build the
installer?
-Original Message-
From: Arun Kumar [mailto:arun_jku...@persistent.co.in]
Sent: 31 January 2011 12:54
To: General discussion for Windows
, Thom Leigh t...@mondago.com wrote:
http://www.tramontana.co.hu/wix/ tutorial on creating installers in
WiX.
Use the ServiceInstall element to install services...
http://wix.sourceforge.net/manual-wix3/wix_xsd_serviceinstall.htm
-Original Message-
From: subrat agasti [mailto:subrat.w
.
Regards,
Arun.
-Original Message-
From: Thom Leigh [mailto:t...@mondago.com]
Sent: Monday, January 31, 2011 6:36 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Migrating from InstallShield to WIX Issue
Does the msi exist in any of the cabs
Is Key a keyword and therefore needs to be placed in square-brackets or
quotes?
I'm confused though - why does the error say that your query is SELECT
[Registry], [Key] FROM Registry but your query is only SELECT Key FROM
Registry? *shrug*
-Original Message-
From: Subhasree Ramesh
The MSDN page for IUniformResourceLocator::SetURL details these return
values...
S_OK: The object's URL was set successfully.
E_OUTOFMEMORY: There is not enough memory to complete the operation.
IS_E_EXEC_FAILED: The URL's protocol handler failed to run.
URL_E_INVALID_SYNTAX: The URL's syntax is
FYI Bhavik, codepage 65001 is UTF-8, but Windows Installer doesn't support it.
Specifically, when I've used it, it messed up the fonts in the Basic UI when
uninstalling (showed squares) which I kind of worked around by making it show
the Maintenance dialog when uninstalling from ARP. In the
When you say never removed even on rollback, do you mean never removed
on uninstall either?
If so, you can set your component's guid to an empty string. Meaning
Windows Installer will not manage the component at all - so it won't
be able to remove it.
But Windows Installer also won't be able to
Specifically, Companion Files are the only things that get written
without regard to versioning. So maybe make the default settings file a
Companion File of another feature that *will* always get installed on a
re-install?
-Original Message-
From: Rob Mensching
Have you tried Component/@Win64=yes for that component?
Not sure if that's needed if you're following robmen's advice and using
-arch, as that switch should set Win64=yes for you (I think?)
-Original Message-
From: Manoj Jangid [mailto:jangi...@gmail.com]
Sent: 21 January 2011 16:12
Like you say, multiple MSIs means updates/patches are a headache. You
could instead use instance transforms. From
http://msdn.microsoft.com/en-us/library/aa369523(VS.85).aspx:
you can install multiple instances of a product if you have a separate
installation package for each instance of a
Google the WixUtil extension. Specifically the Group and GroupRef
elements, and the User element.
http://wix.sourceforge.net/manual-wix3/util_xsd_groupref.htm says
GroupRef is used to join a user to a group.
Hopefully that'll be enough to help you do it...
-Original Message-
From:
http://wix.sourceforge.net/releases/
(there is one folder for 3.0.5419.0)
-Original Message-
From: MeCoco [mailto:vcotirl...@hotmail.com]
Sent: 14 January 2011 16:25
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] WiX source code download
Hi all,
I want
As this is a pre-requisite I'm glad you're plan is to block the install
from the MSI with a meaningful error message if Java isn't installed.
That is definitely the right thing to do.
Fortunately the Java installer is MSI based (or at least the one
installed on my PC is), so detecting it from
This type of thing has been asked about before and as far as I
understand it is not possible - due to limitations in Windows Installer
itself, not WIX.
Instead, consider always having Next enabled, and then when the user
clicks Next, display an error message if either textbox is empty.
-
From: Leonidas Spyropoulos [mailto:leonidas.spyropou...@formicary.net]
Sent: 12 January 2011 15:46
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Condition check and Next Button
On 12/01/2011 15:14, Thom Leigh wrote:
This type of thing has been asked about before and as far as I
Property Id=ARPNOMODIFY Value=1 /
/UI
UIRef Id=WixUI_Common /
/Fragment
/Wix
Then I have WixUIExtension included in the reference section of my VS
2008 project. Again, this is a C++ console application rather than .Net.
-Brad
On Jan 7, 2011, at 12:25 AM, Thom Leigh
Perhaps you should specify the attribute in your XPath query, something like:
ElementPath='//configuration/appSettings/add[key=MatrixPath]'
Or I think '//configuration/appSettings/add[2]' would be for the second add
node...
-Original Message-
From: Sascha Trenz
I think this is what you're after.
To reinstall even if the same version is already installed, I use this in my
Upgrade node:
UpgradeVersion Minimum=!(bind.FileVersion.UCClient.dll) IncludeMinimum=no
OnlyDetect=yes Property=NEWERVERSIONDETECTED /
UpgradeVersion Minimum=1.0.0.0
This is how I do it in my (working) customized minimal UI, using WiX
3.5...
In the main Product wxs:
UI
UIRef Id=WixUI_NoWelcome /
UIRef Id=WixUI_ErrorProgressText /
/UI
My customized UI wxs (which, coincidentally, simply removes the Welcome
dialog from the standard minimal UI. So I'm
Well, WiX is used to build MSIs (and MSMs etc). It can certainly build
MSIs that uninstall old version/upgrade to new version including
services and adding new files. But you'd have to do the rest yourself
(AFAIK?)
Have you not looked at ClickOnce?
I doubt it's possible, it seems to go against the spirit and the letter of the
Windows Installer SDK documentation at:
http://msdn.microsoft.com/en-us/library/aa372391(v=vs.85).aspx
Maybe you should make your own custom ui? As ever tramontana's tutorial is
probably useful for you:
Relates to this:
http://sourceforge.net/tracker/?func=detailaid=2951181group_id=105970;
atid=642714
See here for info:
http://www.joyofsetup.com/2010/04/04/bug-hunting/
http://www.joyofsetup.com/2010/05/20/its-time-to-experiment/
http://www.joyofsetup.com/2010/05/28/experimental-results-part-i/
This isn't what you want but might help you make a start:
util:XmlConfig Id='create.DbInstance' Action='create'
ElementPath='/Settings' VerifyPath='/Settings/DbInstance'
File='[#settings.xml]' Name='DbInstance' Node='element' On='install'
Sequence='1' /
util:XmlConfig
I had a thing like that a couple of months ago. Product/@Codepage would
be 1252 no matter what I set it to, even if setting it to something
totally different like 1256.
I opened a bug in the tracker and I think it got fixed. Which weekly are
you using? Have you tried it in Escrow 2?
PS I was
3.6.
I also notice that you don't even need to use anything in the
WixUIExtension just add a votive reference and it changes the codepage.
Dave
-Original Message-
From: Thom Leigh [mailto:t...@mondago.com]
Sent: 10 December 2010 13:45
To: General discussion for Windows Installer XML
Hi
I've just come across a few bugs in the wix-ui localization files that
were preventing me building various cultures. The bugs are all simple to
fix, mostly just typos. I've added them to the bug tracker on sf, with
instructions on how to fix. I would submit patches but don't know how...
36 matches
Mail list logo
