On 2/18/2010 7:41 AM, Tom Crozier wrote:
> To keep the size of the released installer small do I need to create and
> release a patch instead of the full installer?
>
If you want to ship a subset, yes, you're looking at patches.
> With the recommended installer option to perform the above wh
On 2/18/2010 10:44 PM, Elisabeth Yusnita wrote:
> I have a question about installing apache tomcat as prerequisite using WiX
>
That's really driven by what the Tomcat installer can do. What does the
Tomcat team recommend?
--
sig://boB
http://joyofsetup.com/
---
On 2/19/2010 4:37 AM, Jacek Pospychała wrote:
> Do you know what extra does the installer do, that takes so much time?
It supports rollback which entails extra bookkeeping to be able to
restore files on failure.
> And
> does it make any change if I e.g. split it to more features, or more
> compo
On 2/18/2010 7:47 AM, Tobi Ha wrote:
> Is there a good and secure way to detect if another MSI installation is
> allready running before starting another one which would fail with Error Code
> 1618?
>
No. And another installation could start immediately after such a check
anyway.
> Additio
On 2/17/2010 8:49 AM, Michael Urman wrote:
> You can't change the type of an existing column, but you can add new
> columns in a transform. Patches are built on transforms, so they
> should be just as capable. As I understand it, the ExtendedType column
> was added (instead of a widened Type column
On 2/19/2010 9:36 PM, Sachin Dubey wrote:
> As per the article
> (http://msdn.microsoft.com/en-us/library/aa371175(VS.85).aspx) , I am setting
> REINSTALL = Feature1,Feature2 on VerifyReady dialog.
>
> Like this --
>
>Value="Feature1,Feature2">
>
The Reinstall control event isn't the sam
On 2/19/2010 4:39 AM, Bimali Ponnamperuma wrote:
> does "Order" attribute plays any role here?
>
Yes. See the MSI SDK ControlEvent documentation.
--
sig://boB
http://joyofsetup.com/
--
Download Intel® Parallel Stud
On 2/19/2010 8:13 PM, Sharath P R wrote:
> The above was for a CN Pseudo-Loc build. Does Wix V3 flag usage of
> non-codepage characters as errors now?
>
There were many enhancements in WiX v3 for codepage handling.
--
sig://boB
http://joyofsetup.com/
--
On 2/17/2010 10:42 AM, Jake Boone wrote:
> I have a custom action where I'm trying to use SourceDir.
See the MSI SDK for details about SourceDir; it's not always available.
--
sig://boB
http://joyofsetup.com/
--
Downlo
Your .wixpdb file contains a "filespec" (path reference) of the icon file,
not the file's contents itself. Because either pyro is running from a
different directory than light had been run from when the wixpdb was created
or the directory containing the wxs file that references ControlPanel.wxi is
For "small updates", if you want to use the PatchFamily/@Version sequence to
exclude older patches from the same family set the Supersede attribute to
"yes" in QFE2. This will cause QFE2 to replace all previous patches in the
same family (including QFE1).
-Original Message-
From: Lian Jian
Short of changing their merge module I would think the easiest would be to use
something like WiRunSQL.vbs after light.exe completes before you sign your MSI
and change the sequence number for CollectUserInformationDlg.GUID_GUID_GUID in
the InstallUISequence table to 1297 or thereabouts.
-O
I've been using Linq to XML for the last 9 months or so and find it to be
heaven for doing this type of stuff. Hopefully I'll be able to share something
soon.
--- On Thu, 2/11/10, Matt Lynch wrote:
> From: Matt Lynch
> Subject: [WiX-users] Programmatically edit .wxs files through CodeDomRea
13 matches
Mail list logo
