This seems to have worked - thanks very much.
David
> -Original Message-
> From: Blair [mailto:os...@live.com]
> Sent: 22 December 2009 13:45
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] Setting properties in custom actions
>
>
> The on the com
The sample source code of WiX Tutorial 10.1 has a minor bug, I think.
The listbox has an "Indirect" attribute set to "yes", which prevents
any list items to be displayed correctly, even if you set them by
element inside the control.
So, it should be "no".
---
You could try an "administrative install". You could also try heat.exe's
extraction option.
The APIs involve extracting the cabs and then using the cabinet APIs to
extract the files, for the cases where the files are compressed & embedded.
For external cabs, just the cabinet APIs. For non-compres
What is the "Windows Installer project workspace" you speak of?
The custom action code itself isn't "marked" for one or the other. That
marking is done by the type setting in the CustomAction table for the custom
action (the "InScript" flag). There are differences in what code that is run
as eithe
The only thing you can do is compare the current value of the property
against the known default value. If the command-line value is the same as
the default value you wouldn't ever be able to know.
The only way to know for sure if a property was set from the command-line is
to not have the propert
I tried this option but still the issue exist.
- Nag
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Monday, January 04, 2010 5:22 AM
To: nagara...@symphony.cc; 'General discussion for Windows Installer XML
toolset.'; 'Schrieken, Rene'
Subject: RE: [WiX-users] writing to c
Thanks Blair, that cleans it up nicely.
Blair-2 wrote:
>
> How about this?
>
> (USEINTEGRATEDSECURITY = 1 OR (DBUSERNAME AND DBPASSWORD))"?>
>
> Height="17"
> Default="yes" Text="Next">
>
>
> NOT ($(var.InputValidated))
>
>
>
I come up with slightly different idea. I have two properties defined as
follows:
MYPROPERTY
And then in custom action I check whether MYPROPERTY was set.
-Original Message-
From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com]
Sent: Monday, January 04, 2010 1
Hi all, I'm having a bit of trouble reusing dialogs. I'm building an
installer that (optionally) installs two IIS web applications. I need
dialogs for both for selecting website, virtual directory, and app pool. I
did some searching on this list and found
http://n2.nabble.com/Re-using-Dialogs-td11
I hit this problem a few years ago and decided that the added
complexity of trying to reuse dialogs wasn't worth the effort -
development, debugging and maintenance would have been a nightmare.
It was easier to copy/paste the dialog code and the person who took
over the project after me was easily
Is it possible to specify the codepage value at build time based on
the build culture and/or build configuration name?
--
Tony
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizo
That's what I figured. Copy & paste is annoying (I always try to adhere to
DRY :/ ) but I'll live with it. Thanks Wendell.
Wendell Joost wrote:
>
> I hit this problem a few years ago and decided that the added
> complexity of trying to reuse dialogs wasn't worth the effort -
> development, debu
Hi,
I have a component that includes some xml values that are written out
using XmlFile. I want to be able to rerun the installer and change the
values without changing the install state of the component, but it seems
that it only writes the values when the component is going from
uninstalled to
Something like this?
int SendSampleICEMessage(void)
{
PMSIHANDLE hRecord = MsiCreateRecord(1);
UINT error = MsiRecordSetString(hRecord, 0,
"Name of ICE\tMessage Type\tDescription\tHelp URL or location\tTable
Name\tColumn Name\tPrimary Key\tPrimary Key\tPrimary Key . . . (repeat for
as ma
Easiest way is via .WXL files. Since each can contain just one culture you
simply use that file to set the codepage (and don't set the codepage in the
database code itself). The biggest limitation with this idea is you can't
directly set the summary codepage this way, but you can use loc variables
What do we need to include in a patch WXS file to let WIX know that the patch
should include a new dialog that is added to the installer UI? I tried this
with UIRef element under PatchFamily, with the ID of the dialog, but it does
not seem to include it in the patch.
Thanks,
Sharat Janapareddy
Most patches should not have any references under PatchFamily (nor more than
one PatchFamily). That will cause ALL changes between the target and
upgraded images to be included in the patch.
Some (generally very large and complicated) setups require scoping the
changes into groups/series/buckets w
Hello,
I have built and msi for installing a bunch of custom windows
services using visual studio setup. During install use the visual studio
custom actions radio button to allow the user to choose 'Dev/Prod/Trn/QA'. I
use this context parameter in my service installers to modify the servic
Blair, if we don't have ANY references under PatchFamily, how can we tell WIX
which change should be included in the patch? Without listing every changed
component/property/etc. in the patch WXS file, none of the changes are making
to the final MSP.
FYI, I am able to patch custom actions, compo
The last time I built an MSP file, I had only one PatchFamily and it had NO
children at all. I built it this way:
To have the PatchFamily in a different fragment from the Patch element (as
you have) you would need to include an appropriate PatchFamilyRef to pu
Look at InstanceTransforms element?
-Original Message-
From: angela jones [mailto:suggestionang...@gmail.com]
Sent: Monday, January 04, 2010 3:37 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] multiple instances wix source code
Hello,
I have built and msi for install
Thanks for the explaining that Blair. I already have everything in place for
the PatchFamily and PatchFamilyRef. So, that part is good and I am able to
generate the patch without any issues.
The only thing that I am not sure is if I can use the UIRef for including a new
dialog (added to the upd
Repair the Component.
On Mon, Jan 4, 2010 at 11:57 AM, Kevin Garman wrote:
> Hi,
>
> I have a component that includes some xml values that are written out
> using XmlFile. I want to be able to rerun the installer and change the
> values without changing the install state of the component, but i
My primary role in the WiX-based patching solution was adding the "-delta"
switch to Pyro, along with all the related authoring changes and
implementation. Since the products I worked with all went the "simple" route
with regard to patching I never used, except for an experiment or two, any
patch f
It looks like MsiProcessMessage works only in case if CA is called through
UI Sequence, it returns 0 (No action was taken) while the CA is called
through control event, below posting has similar issue
http://www.mombu.com/microsoft/platform-sdk-msi/t-how-to-check-whether-a-ca-
is-called-by-a-contr
25 matches
Mail list logo
