Visual Studio's MSMs are already notorious for being poorly written, but there
are several blogs from Microsofties and others closely connected with the VS
team that will post mentioning which warnings can be ignored from their MSMs.
For anyone else, please ask the author of the MSM, and if you
There is a fair bit of debate about the propriety of including the policy MSMs.
Some argue that they should be included (MS does ship them as MSMs, after all)
so that everyone will benefit from whatever the latest-and-greatest the user
happens to install (i.e. increase the coverage of MSFT secur
I tried it, however it doesn't work fully for my case. Besides the OS version,
I also need to check the architecture of the OS. I want to block 64 bit package
to be installed on a 32 bit OS. If I set the condition, the installation will
be blocked, however, I didn't see I can customize the erro
At install runtime your BA has access to it as part of the WixBundleProperties
"sub-table" of the BootstrapperApplicationData.xml.
If you need it outside of install-time (the below is subject to change, don't
depend on it):
As an implementation detail: it is contained in that xml file in the
Thank you.
When should I be worried about this warning? Say I add merge module x in two
months and get the same type of warning.
Regards, Lars
> From: os...@live.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 19 Aug 2013 09:10:17 -0700
> Subject: Re: [WiX-users] LGHT1055 Merge module
Thank you for your reply.
Adding the policy merge module solved the issue.
I would consider updating the
http://wix.sourceforge.net/manual-wix3/install_vcredist.htm page, either update
this line "There is generally no need to include the policy MSMs as part of the
installation." or describe
The question was really what is the correct syntax for "variable not equal to
empty string" when used with DetectCondition? (I don't think the syntax for
this is documented so will add it when I know the correct syntax.)
Some options:
Variable <> ""
Variable != ""
Variabl
Bundle\@Condition attribute.
The limited conditions it can evaluate include OS.
> From: naz...@microsoft.com
> To: wix-users@lists.sourceforge.net
> Date: Tue, 20 Aug 2013 05:12:55 +
> Subject: Re: [WiX-users] Wix Burn: Bundle condition does not work if using MBA
>
> Hi,
>
> I met with t
I think we should make that error message more clear. Please file a bug.
> From: jo...@msli.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 19 Aug 2013 14:00:08 -0700
> Subject: Re: [WiX-users] disassemble a bundle
>
> I see I had to make a directory and extract into it
> dark.exe -x foo
Hi,
I met with the same problem with the MBA precheck. Definitely, I can have the
code in my MBA to check the pre conditions, however, I think the following
scenario is totally broken. Eg. We want to block installation of our product
on the OS vista or before.
A user uses a vista machine wi
I sign the bundle I get this error.
An unsigned bundle seems to work.
On Mon, 2013-08-19 at 15:36 -0700, jo...@msli.com wrote:
> Looks like my log file was stripped out
>
> [0EA8:0208][2013-08-19T14:44:54]i001: Burn v3.7.1224.0, Windows v6.1 (Build
> 7601: Service Pack 1), path:
> C:\Users\buil
Looks like my log file was stripped out
[0EA8:0208][2013-08-19T14:44:54]i001: Burn v3.7.1224.0, Windows v6.1 (Build
7601: Service Pack 1), path:
C:\Users\build\Desktop\MyProgram-3.1.0-3776-Installer.exe, cmdline:
'-burn.unelevated BurnPipe.{A7261C75-BACC-4401-B5F3-42EEC22098B5}
{F94F9B48-9AB8-
Before InstallInitialize, yes, true. Typically though there are more
occurrences after InstallFinalize because that's one of the documented
options:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa371197(v=vs.85).aspx
which looks attractive because of those magic words "most efficient" bu
I am trying to figure out what is wrong with a bundle created in my
auto-build system.
I have created 2 bundles with the same scripts and files files, that
differ only in how the scripts where run.
The bundle created by the auto-build system has error 0x80004005
-Unspecified error (see attached l
Or before InstallInitialize. REP must be within the install transaction.
Dave
From: Phil Wilson
To: afor...@cmu.edu; General discussion for Windows Installer XML toolset.
Sent: Monday, August 19, 2013 2:53 PM
Subject: Re: [WiX-users] Restore previous windo
When you say "previous windows service" does that mean that you doing an
upgrade? If so, it should just work, unless you have RemoveExistingProducts
after InstallFinalize.
On Mon, Aug 19, 2013 at 10:42 AM, Alain Forget wrote:
> Add the "Start" attribute to the ServiceControl element?
>
> Alain
A couple of other things to look at, assuming you've looked at Blair's
comment:
One issue with these SxS Dlls is that the policy merge module makes a
difference. IIRC, the VC redist exe will install the Dlls and the policy
file that redirects requests to the appropriate Dll. So I'd add the policy
Ok, if that's so then I misunderstood.
On Sun, Aug 18, 2013 at 8:25 PM, dave wrote:
> Hi,
>
> The code I've used for an MSI doesn't work with a Wix bundle. I don't
> believe it's the same format as MSI so property tables aren't relevant?
>
>
>
> --
> View this message in context:
> http://windo
Two ways:
1. Follow the directions in the chm for "msbuild daily builds".
2. Install the resulting installation exe.
Your choice.
Kenneth Porter wrote:
--On Monday, August 19, 2013 10:50 AM -0700 Kenneth Porter
wrote:
> Aha. I ran MSBuild in .\tools and it ran both 32 and 64 bit versions of
I guess that makes sense (will try shortly) ... but what about not including
the Framework in the setup?
I just want to provide DownloadUrl and let it does the rest of the job which
is to DL the FW and install in background and then finally start my .MSI.
Thank you so much guys
--
View this mess
I see I had to make a directory and extract into it
dark.exe -x foo MyProgram-3.1.0-3776-Installer.exe
On Mon, 2013-08-19 at 13:52 -0700, jo...@msli.com wrote:
> I ask because dark didn't work for me.
>
> $ dark MyProgram-3.1.0-3776-Installer.exe
> Windows Installer Xml Decompiler version 3.7.12
I ask because dark didn't work for me.
$ dark MyProgram-3.1.0-3776-Installer.exe
Windows Installer Xml Decompiler version 3.7.1224.0
Copyright (C) Outercurve Foundation. All rights reserved.
MyProgram-3.1.0-3776-Installer.exe
dark.exe : error DARK0001 : Value cannot be null.
Parameter name: path
Don't have to be in separate files.
On Mon, Aug 19, 2013 at 12:44 PM, Marlos Gottschild <
marlos.gottsch...@gmail.com> wrote:
> Works like a charm. Thanks Rob and Philippe.
>
> For future reference, I moved both ComponentGroup and Feature to a separate
> file, not only ComponentGroup.
>
> Thanks
Works like a charm. Thanks Rob and Philippe.
For future reference, I moved both ComponentGroup and Feature to a separate
file, not only ComponentGroup.
Thanks again.
BR,
Marlos
2013/8/19 Rob Mensching
> An entire Fragment is included when referenced.
>
>
> On Mon, Aug 19, 2013 at 12:15 PM, M
If you have access to the wixlib's code and can modify it, I'd suggest
putting one feature per fragment and then using FeatureRef to import the
ones you need.
On 19/08/2013 3:19 PM, Rob Mensching wrote:
> An entire Fragment is included when referenced.
>
>
> On Mon, Aug 19, 2013 at 12:15 PM, Mar
What you really want is for your UI to be displayed. You need to set the
MsiPackage@DisplayInternalUI attribute set to "yes". The default is "no".
--
John Merryweather Cooper
Build & Install Engineer -- ESA
Jack Henry & Associates, Inc.(r)
Shawnee Mission, KS 66227
Office: 913-341-3434 x79101
Hmm I am afraid I don't understand you Rob. I built a bootstrapper project
and set the application setup as well as fw .net 4.0 ...
My app setup has 4-5 steps/dialogs but when I put it in the bootstrapper
it's installed in background which is not what I want.
I want the following:
1. checks if .N
An entire Fragment is included when referenced.
On Mon, Aug 19, 2013 at 12:15 PM, Marlos Gottschild <
marlos.gottsch...@gmail.com> wrote:
> Hi,
>
> I have a wixlib with Components, ComponentGroups and Features and another
> wix project referencing this library. And I need to selectively choose
>
Hi,
I have a wixlib with Components, ComponentGroups and Features and another
wix project referencing this library. And I need to selectively choose
which Features from the wixlib I will include in my main setup. This way:
wixlib:
file1.wxs
file2.wx
Just like everything else: dark.exe.
On Mon, Aug 19, 2013 at 11:44 AM, jo...@msli.com wrote:
> Is there a way to disassemble a bundle?
>
>
>
> NOTICE: This email may contain confidential information. Please see
> http://www.meyersound.com/confidential/ for our complete policy.
>
>
> --
When I added the WixExtendedBootstraperApplication to my Wix 3.7.1224
installation, I downloaded the zip package from:
http://wixextba.codeplex.com/releases/view/105895
And I put the one DLL in that package into my Wix Toolset 3.7.1224\bin
folder.
At a later point I did what I described in an
Is there a way to disassemble a bundle?
NOTICE: This email may contain confidential information. Please see
http://www.meyersound.com/confidential/ for our complete policy.
--
Introducing Performance Central, a new si
WiX toolset install does.
On Mon, Aug 19, 2013 at 11:26 AM, yugolancer wrote:
> Hi Guys,
>
> Would you show me an example of bootstrapper which simply checks on start
> if
> .NET 4.0 is installed and install if not and THEN just start my regular
> setup AS IS without installing it in background
Hi Guys,
Would you show me an example of bootstrapper which simply checks on start if
.NET 4.0 is installed and install if not and THEN just start my regular
setup AS IS without installing it in background.
Currently it does install the SETUP silently so the user cannot interact
with it which i
--On Monday, August 19, 2013 10:50 AM -0700 Kenneth Porter
wrote:
> Aha. I ran MSBuild in .\tools and it ran both 32 and 64 bit versions of
> sn to exclude everything from verification, and now the non-elevated
> build seems to be proceeding to completion.
I tried this on a second system, run
Add the "Start" attribute to the ServiceControl element?
Alain
-Original Message-
From: Андрій Цьок [mailto:andrey.t...@gmail.com]
Sent: Monday, August 19, 2013 13:35
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Restore previous windows service if ne
I would like to know when WiX 3.8 will become a published released build?
We normally upgrade when a release is published and therefore was wondering
if there is a schedule when 3.8 will be released?
We are trying to create a Burn .exe with translated UI and 3.7 currently has
a bug in it that pre
I used wix functionality
http://schemas.microsoft.com/wix/2006/wi"; />
http://schemas.microsoft.com/wix/2006/wi"; />
On Mon, Aug 19, 2013 at 8:03 PM, John Cooper wrote:
> How are you registering the Windows service? If you're using
> InstallUtil.exe, you'll need to roll your own rollback--
Okay, when I installed the latest WiX 3.8 and Updated my project files to use
3.8 the build correctly built in the UI so that on German the UI/EULA is
German, on French it is French and on English and unsupported languages it
shows English.
So yes 3.8 has the fixes in it. So my version of 3.7 has
How are you registering the Windows service? If you're using InstallUtil.exe,
you'll need to roll your own rollback--it won't happen automatically. If
you're using the WiX Service authoring, it should rollback.
--
John Merryweather Cooper
Build & Install Engineer -- ESA
Jack Henry & Associates
How can we restore previous windows service if new installation is Failure ?
After rollback WIX doesn't register old service in Windows Services and
leave it broken.
--
Introducing Performance Central, a new site from Sourc
--On Monday, August 19, 2013 10:25 AM -0700 Blair Murri
wrote:
> wix-devs mailing list has more history regarding building the toolset.
Thanks. Just signed up for that.
> src\tools needs to be built once elevated before you build the toolset.
> You don't need to use OFFICIAL_WIX_BUILD if you w
Well, I am sorry to hear that it is not working for you. Since I can build
it with 3.7 and it works, I think I would try to use ProcessMon or WinDbg to
figure out what the issue is, focusing only on the German Wix 3.7 exe which
I complied for you and your compilation of the same thing. Originally
wix-devs mailing list has more history regarding building the toolset.
src\tools needs to be built once elevated before you build the toolset. You
don't need to use OFFICIAL_WIX_BUILD if you will run the build on the same box
as you built it.
> Date: Mon, 19 Aug 2013 09:03:54 -0700
> From: sh
Please file a bug to get a better error report.
> From: ingoderfisc...@hotmail.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 19 Aug 2013 12:44:10 +0200
> Subject: [WiX-users] png as IconSourceFile causes Arithmetic operation
> resulted in an overflow.
>
> Not sure if this is right plac
Torch requires that its inputs all be in the same format. Create all of your
MSIs in WIXOUT, then run your base through light again to generate that MSI.
Pass only WIXOUTs to torch.
> From: edoming...@goalsystems.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 19 Aug 2013 12:14:21 +0200
Okay after getting your install to build I test and it will still not show
German or French licenses on German and French systems. This is still
building with WiX 3.7 and having the updated WiXBalExtentionExt.dll file
into my WiX 3.7 bin folder.
So just having no luck what so ever.
I'll look at i
That particular CA will accommodate the data from both merge modules, so its
inclusion just one time is OK (and correct in this case). Ignore this
particular warning.
> From: laasu...@hotmail.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 19 Aug 2013 13:59:41 +0200
> Subject: [WiX-users
Did the merge module come from the same service pack level of Visual Studio as
was used to build the application?
> From: laasu...@hotmail.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 19 Aug 2013 11:34:36 +0200
> Subject: [WiX-users] Merge module not working
>
> Using Wix 3.7
>
> I
I want to debug the problem I'm having with ExePackage/@DetectCondition so
I cloned the current git trunk and attempted to run MSBuild on it. I'm new
to assembly signing but I think I have my head around the principles from
reading a bunch of blogs about it, including the need to use the 64 bit
Well, on a "Repair", a previously installed component is going to be
reinstalled. By default, component conditions are considered only once. You'd
need to make the Component Transitive. But then you're going to run into the
situation where the component may uninstall under certain circumstanc
I have a conditional component and the conditional statement is created via
a custom actin that is run in the Install Execute Sequence before the
CostFinalize action. However the component is always getting installed
regardless of the condition.
My Condition: PROMPTLOCKMODE = "0"
I have che
I don't think it is due to the pdb my understanding is that it is because
wixstdba is not loaded at startup so windbg hasn't read the pdb at that stage,
once wixstdba is in memory then the pdb has been read and you can set break
points - I see exactly the same thing if I build the pdb myself.
N
You want DetectCondition. InstallCondition says whether a package should
be installed on the machine. If false and the package is installed, it will
uninstall the package.
On Mon, Aug 19, 2013 at 7:21 AM, Kenneth Porter wrote:
> --On Monday, August 19, 2013 8:01 AM -0700 Phill Hogland
> wrote:
Be very, very careful using ADDLOCAL and friends directly on the
command-line. You can really get confused behavior in the MSI if you get
that wrong. You'll want to test lots and lots of scenarios (install,
uninstall, patch, repair upgrade) with all the different permutations.
On Mon, Aug 19, 201
After doing this experiment with your code and demonstrating that
automatically detecting languages works using WiX 3.7, even without
specifically using the WiXExtenededBootstraperApplication, I switched my
main project (seven languages) back to Wix 3.7. I did limited testing on my
Windows 8 test
Placing the WiXBalExtentionExt.dll file into my WiX 3.7 bin folder did not
make a difference. So was there anything else you had to do or did to make
this work?
Can both 3.7 and 3.8 reside on the machine at the same time? If as you said
that 3.8 already has the fix in it then I was thinking of ins
--On Monday, August 19, 2013 8:01 AM -0700 Phill Hogland
wrote:
> It seems like you would want to use DetectCondition to determine if the
> package already exists and InstallCondition to determine when you want to
> launch the exe.
If the prerequisite package is not installed, I want to run its
No, but I had a similar issue and determined that Symantec is assuming that
if the package does not have a valid Code Signing signature it is a virus.
There is no virus, it is a FALSE Positive which many others have also had
issues with. If you use your code signing certificate to sign the bundle
Well I was told that there is a bug that affects this issue in WiX 3.7 (which
you can resolve by adding the WixExtendedBootstrapperApplication from
http://wixextba.codeplex.com/releases/view/105895) or by switching to WiX
3.8. My development box is configured so that by changing an environment
var
It seems like you would want to use DetectCondition to determine if the
package already exists and InstallCondition to determine when you want to
launch the exe.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ExePackage-DetectCondition-syntax-tp75
I know that there are a number of different approaches that one might take to
address this question. One approach might be to use something similar to
Example #11, at:
http://wixextba.codeplex.com/releases/view/105895
Which involves a bundle that displays radio buttons and then use that
exclusiv
Ok Phill, I was able to download and extract the files from your zip. I tried
out both .exe that you created and created a German VM to test on. They did
show the German EULA and when I switched to my French image it showed the
English EULA.
I then updated your German .wxl file with German text st
Yes I had a similar problem setting a breakpoint, but I did not realize it
was due to the pdb. When WinDbg launches the exe it breaks and gives me a
chance to set a breakpoint. I would not show the breakpoint that I tried to
set with F9 after placing the cursor at LoadBootstrapperBAFunctions() (
The WIX configuration below produces two warnings:
warning LGHT1055 : The InstallExecuteSequence table contains an action
'SxsInstallCA' which cannot be merged from the merge module
'C:\path\path\Microsoft_VC80_CRT_x86.msm'. This action is likely colliding
with an action in the database that is
Not sure if this is right place for this post but it took me some time to find
the cause of the error:
light.exe(0,0): error LGHT0001: Arithmetic operation resulted in an overflow.
I put a png-file to the IconSourceFile-Property in stead of an ico-file. (
copy/paste mistake )
Hi all,
I'm building a multilanguage msi; for doing that I'm generating all msi
cultures I need and then getting msts using torch. My msi it's big and making
all cultures it's slow so I thinking build first base msi ('neutral' lang as
en-US) and doing all others as wixout like this (showing span
I would expect DetectCondition="ub5Present" to work then. Have you tried 'NOT
ub5Present = ""'?
Hopefully someone else will jump in and confirm the syntax.
Neil
-Original Message-
From: Kenneth Porter [mailto:sh...@sewingwitch.com]
Sent: 19 August 2013 10:22
To: General discussion for
Using Wix 3.7
I added Microsoft_VC80_CRT_x86.msm merge module to my wix setup according to
http://wix.sourceforge.net/manual-wix3/install_vcredist.htm
I tested the new msi file on a clean WinXP SP3 machine. Installed the product
and when I started the application I get "The application failed
--On Monday, August 19, 2013 7:42 AM + Neil Sleightholm
wrote:
> Just to be clear if DetectCondition is true it means the package is
> already installed. In your case "ub5Present" has a value of
> 'C:\Windows\system32\' does that mean it isn't installed?
Empirically, it appears that utils:C
Hi,
It must have been something with copy&paste. Now it works. Thx.
So, in WiX3.7 it is not possible yet to use detected language automatically?
BR,
Branko
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
71 matches
Mail list logo