Hello,
I've created msp patch for my product.
It must convert 3.1.4 version to 3.1.5
After I install it, it updates all needed files, changed in 3.1.5,
except one file.
This file is key file of component, containing only this file.
How can I explore why it is happening?
When I open msp file in O
On 27-Jan-12 09:55, DuBois, Joseph wrote:
> As you can see from the snipet below I am attaching the ALLUSERS to the
> individual packages, but not sure how to attach it to the BUNDLE.
>
Right but if WiX, while building the bundle, thinks that all your
packages are per-user, it will ma
On 27-Jan-12 12:53, Neil Sleightholm wrote:
> On XP you get a UI that looks like the standard BA UI - although my XP
> machine didn't have .Net4 on it.
Ah, yes, that's the WixStdBA in pre-req mode. Any managed BA gets it to
bootstrap .NET 4.0 if necessary before trying to load the managed BA
ass
Can your MSI use the Windows Installer SourceDir property? When installing
it should be set to the directory where the MSI and its attendant files were
cached.
Blair
-Original Message-
From: Romeo S. [mailto:dfox.mxyzp...@gmail.com]
Sent: Friday, January 27, 2012 5:39 PM
To: wix-users@li
Hi,
How do I find out what is the current cached directory used by my BA? I Need
to pass some properties to my MSI which is a complete path of a file that is
compressed and cached to the BA.
I don't see any StringVariables in the Burn log file that I can use at
runtime.
Thanks,
Romeo
--
View th
Is there any chance you could put a date and/or a changeset number by each
release so we can see easily what's new in each one?
Thanks,
Pete
--
Try before you buy = See our experts in
Do you possibly need to add the ForcePerMachine attribute to your MsiPackage
elements?
Blair
-Original Message-
From: DuBois, Joseph [mailto:joseph.dub...@childrens.harvard.edu]
Sent: Friday, January 27, 2012 6:56 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
Maybe I miss-stated.
As you can see from the snipet below I am attaching the ALLUSERS to the
individual packages, but not sure how to attach it to the BUNDLE.
Thanks for any help.
Joe
http://schemas.microsoft.com/wix/2006/wi";
xmlns:netfx="http://schemas.microsoft.com/wix/NetFxExte
On XP you get a UI that looks like the standard BA UI - although my XP machine
didn't have .Net4 on it.
Neil
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: 27 January 2012 16:27
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Install 3.6 on clean VM
On 27/01/2012 15:59, John Bergman wrote:
> Where did you get the merge module for the VC 10.0 Runtime? I have been
> looking for one for quite some time.
If you have Visual Studio 2010 installed, it's in C:\Program Files
(x86)\Common Files\Merge Modules
--
Bruce Cran
On 27-Jan-12 07:00, Neil Sleightholm wrote:
> To help me provide some more information on this bug (no text on install UI)
> could someone let me know what is required on Windows 7 to enable the UI to
> work?
.NET v4
> I am assuming there is something as the same UI does not appear the same on
On 27-Jan-12 04:14, Joost van Zoest wrote:
> I have made an installer in WIX which embeds 2 merge modules: the
> Microsoft_VC100_CRT_x86.msm merge module, and my own module (let's call
> this one MyMergeModule.msm for now). When I embed the VC merge module
> before MyMergeModule, I get a lot of wa
Where did you get the merge module for the VC 10.0 Runtime? I have been
looking for one for quite some time.
John
-Original Message-
From: Joost van Zoest [mailto:jzo...@siqura.com]
Sent: Friday, January 27, 2012 3:14 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Visual C
To help me provide some more information on this bug (no text on install UI)
could someone let me know what is required on Windows 7 to enable the UI to
work? I am assuming there is something as the same UI does not appear the same
on Windows XP.
Thanks
Neil
Neil Sleightholm
n...@x2systems.co
I have made an installer in WIX which embeds 2 merge modules: the
Microsoft_VC100_CRT_x86.msm merge module, and my own module (let's call
this one MyMergeModule.msm for now). When I embed the VC merge module
before MyMergeModule, I get a lot of warnings that some actions can not
be merged from MyM
Torch marks up the database changes. Including -p causes it to leave the
unchanged portions of the database intact so they will be present for Pyro
to use in its processing.
It is Pyro that looks at the two files and determines if they are the same
or not, and it "promotes" files that compare as d
An MSI file is a document, not an executable.
-Original Message-
From: Andrew Collier [mailto:acoll...@gmx.com]
Sent: Thursday, January 26, 2012 8:47 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix Bootstrapping Issues
If I build a use msbuild to
As per this post
http://stackoverflow.com/questions/8691061/wix-3-6-burn-bootstrapper-fails-to-elevate
On Fri, Jan 27, 2012 at 4:40 AM, Bob Arnson wrote:
> On 26-Jan-12 11:18, Boyd Ludlow wrote:
> > I know that a bug currently exists when using burn that it errors rather
> > than asking for elev
18 matches
Mail list logo
