Take a look at the InstanceTransforms element.
On Mon, Mar 21, 2011 at 9:14 PM, IrishGlugg wrote:
> Could anyone help me understand what this changeset comment means, "Support
> MultiInstance Component in instance transforms"? I saw it in the commits
> on
> codeplex on 3/20 by Rob, but when bro
I think you found a bug in the UI sequence. Would you please file the bug so
it is tracked and can be fixed. Thanks.
On Thu, Mar 24, 2011 at 6:51 AM, Bruce Cran wrote:
> On Thu, 24 Mar 2011 13:43:38 +
> "Skildum, Mathew" wrote:
>
> > Just because WIX ships a set of UI dialogs does not mean
You need to get the Component with your SQL content to be repaired. I expect
the log file is saying the Component is being skipped because it is already
up to date. You may need to explicitly set the ADDLOCAL property to force
your Component to install (IIRC).
On Wed, Mar 23, 2011 at 6:16 AM, Tobb
Neverheard of this sort of requirement. I believe you'll have to redefine
the custom action yourself. Probably a good bit of work... but I've never
tried.
On Thu, Mar 24, 2011 at 10:52 PM, Syama Rajendraprasad <
syama...@microsoft.com> wrote:
> Hi
>
> The SQLScripts are run when executing Execute
You can ship your patches as plain .msp files or you can wrap the .msp files
in another Bundle (great if you need to apply multiple patches or want to
show a custom UI).
On Sat, Mar 26, 2011 at 5:28 AM, Sean Farrow
wrote:
> Hi:
> I'm currently writing a bundle using burn. Later on we will need to
I often use depends.exe if a CustomAction is failing to log anything (all
the WiX custom actions log specific errors on failure).
On Thu, Mar 24, 2011 at 8:30 AM, Liam Flanagan wrote:
> Hello,
>
>
>
> I have a custom action function written in C that is called from a Wix MSI.
> This custom action
This might help:
http://robmensching.com/blog/posts/2007/4/27/How-to-create-an-uninstall-shortcut-and-pass-all-the
On Mon, Mar 21, 2011 at 6:14 AM, MYFLEX wrote:
> Anybody having the following issue?
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabb
I read about that, as stated by Neil,
useLegacyV2RuntimeActivationPolicy must be set to true to prevent
issues
(http://siderite.blogspot.com/2010/07/msi-custom-action-error-2896-on-windows.html).
But if I want the code not to run on FW 2.0 is it possible to not
allow the Runtime by commenting the
For Product/@Language decimal LCID representation is needed and here
16393 (en-IN) is not allowed. As I understand WiX uses the parent
language for special Locales like e.g. German(German) for
German(Austria) and German(Switzerland) to serve german speaking
installations or en-US for the different
Hi,
At first glance for me the two files product and pacack.xml seem to
have the wrong content.
As you describe your requirements have a look at SQL Server Compact
Edition Prerequisite as it has a similar structure and the intention
to install MSI packages.
Pleaase therefore diff the whole folde
Hi:
I'm currently writing a bundle using burn. Later on we will need to write and
release patches.
As I am using burn, can I use plain .msp/msu files or do I have to use a .exe
file?
Any help appreciated.
Regards
Sean.
--
I am targeting .Net 4 with DTF and have not seen an issue. IIRC
correctly you do need to make an alteration to the .config file as
follows:
Neil
-Original Message-
From: Paden, Patrick [mailto:patrick.pa...@wolterskluwer.com]
Sent: 25 March 2011 22:58
To:
12 matches
Mail list logo
