Aha! That is what I was looking for. I'll play with that, and see if I can
make it work.
Thanks,
Thomas DUe
-Original Message-
From: André Werlang [mailto:and...@gvdasa.com.br]
Sent: 28. august 2009 15:17
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] RE
Thanks Svet, It is working now :)
From: Svet Bonev [sbo...@microsoft.com]
Sent: Monday, August 31, 2009 12:42 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem while creating virtual directory
Jaspreet: Your xmlns
Hi There,
I want to GAC and Register(REGASM.EXE) assemblies. Please share some snippets
Thanks
Jaspreet Singh
***The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged materia
Are all of your feature-dependant custom actions sequenced in the
InstallExecuteSequence table after CostFinalize? If so, you can use the
"&FeatureName=3" style syntax to condition your custom actions.
As to how to conditionalize your features, you can't use a bitmap of
InstallLevel (1: because In
IIRC Microsoft Update only truly supports one MSP per "Product" which is
defined as a ProductCode/ProductLanguage/ProductVersion combo when using the
MSP-based rules. If you are willing to completely "free-form" your
publishing XML (not base it on the MSP file itself) you can get around that.
The
Dear Sebastian Brand,
> When sequencing the custom action, use &MyFeature=3 to
> schedule it whenever the MyFeature feature is being installed.
Thank you for your valuable advice.
At first, I couldn't understand what you mean.
But now, I understand what you mean.
Your advice have really heｌped me
Hi,
My installer is MUI-based MSI file. In other words, the user can use this MSI
file to install the product on machines having different locales and the
installer wizard will show localed text. For example, the installer shows
english string for a machine having en-US locale and shows japanes
Hi,
I've been looking for the same thing, unfortunately even reading from
a plain text file doesn't appear possible - INI and XML files are the
only types of files that you can read/write with standard MSI and WiX
tools.
The solution instead was to modify the application to read/write from
the re
Because text files are "free-form" you either need to specify the exact text
format (.INI, or .XML, or whatever) the text file is in OR you need
something like a SED editor wrapped into a custom action. Having said that,
I don't happen to know of any SED C/As.
However, I'm sure someone would be wi
I've been googling this for a couple days and maybe I'm just not looking for
the right combination of words, so can anyone point me to a custom action
that would let me modify a text file during install? I need to update it
with the selected installation path that the user has chosen.
Thanks!
sli
Let me make sure I'm going to do this right...
(I think I'd end up with about 100 FeatureRefs at the end.)
Say, I have this: (This is the largest of the 10 "toolchain" fragments
that get made, the rest run from 2 to 300 files in size)
And this (this would be an example of one of th
Jaspreet: Your xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension "
declaration has a space character before the closing quote. Remove the space
and try again.
Svet Bonev
Microsoft Corporation
-Original Message-
From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.
Dmitry Berkovich wrote:
> As you can see from example I want install Comp2 only if F1 selected,
> even if F2 selected (Comp2 belong to F2).
>
It needs to belong in both features. MSI won't install it if its parent
feature isn't being installed.
--
sig://boB
http://joyofsetup.com/
Andreas Mertens wrote:
> Back in the main *.wxs file, in your Feature element, simply add a
> FeatureRef element that refers to the Feature of your component group in the
> other file(s).
>
You can also use ComponentGroup/ComponentGroupRef instead.
--
sig://boB
http://joyofsetup.com/
-
Uma Harano wrote:
> Is there any way to do this with WiX?
It's not supported. It's easy to violate component rules.
--
sig://boB
http://joyofsetup.com/
--
Let Crystal Reports handle the reporting - Free Crystal Report
jnewton wrote:
> I was building WiX and noticed that AnyCPU assemblies are outputted to the
> x86 folder. I was just curious as to why this was the case. Its not a big
> deal, just curiosity.
>
Mostly because it's annoying to do it the "right" way. Pretty much
everything is platform-specific ev
Sean Farrow wrote:
> Thanks, are there any sample dialogues with some text, and edit box with
> a label, a checkbox and back, next and cancel buttons?
>
I don't know of any, but there might be some open source projects you
could model after.
--
sig://boB
http://joyofsetup.com/
---
Nicolas Lambert wrote:
> I have an issue with the UAC and IIS clashing.
Vista SP1 and Server 2008 requires elevated rights to read the metabase;
previous versions could read from an immediate CA.
--
sig://boB
http://joyofsetup.com/
---
Andy2k8 wrote:
> How do I create a patch that restarts the existing service followed by the
> files update?
>
Use ServiceControl/@Start="install".
--
sig://boB
http://joyofsetup.com/
--
Let Crystal Reports handle t
Blair,
Thanks for a suggestion. I wasn't aware that such a tool is already
shipped with Windows. I'll definitely give it a try.
Do you happen to know if it does have any prerequisites regarding a
target system? (like certain version of msiexec, MFC libraries, .NET
framework...). That is - can I as
I am new to Wix, but I have done something similar myself. My opinion is to
take that huge feature and identify the various component "groups" (related
functionality). Create a separate .wxs file for each such group of
components and move them into that. Create in each file a single Feature
elem
Right now, I have a 3600+ component feature, and I'd like to know how to
split it up into subfeatures that do not show up on a feature tree.
(when that gets added in - I'm not using it right now.
Here's how it looks right now:
--Curtis
--
Curtis Jewell
swords...@cs
22 matches
Mail list logo
