On 19-May-12 03:54, Neil Sleightholm wrote:
This http://wix.sourceforge.net/manual-wix3/util_xsd_registrysearch.htm says
that util extension RegistrySearch supports @Format=raw and mentions
REG_MULTI_SZ in the @ExpandEnvironmentVariables section but not specifically
in the Format attribute.
On 17-May-12 20:20, Dave Combs wrote:
MSI (s) (9C:24) [17:03:39:948]: Component: CMP_162; Installed: Local;
Request: Absent; Action: Null
That usually indicates something else, expressed earlier in the log, is
preventing the requested action, such as violating the component rules.
Try it in
On 16-May-12 12:52, Martin Sustrik wrote:
C:\Users\me\libxs\foo.wxs(98) : error LGHT0103 : The system cannot find
the file 'foo.h'.
See How To: Specify source files in wix.chm.
--
sig://boB
http://joyofsetup.com/
--
On 16-May-12 05:28, Pally Sandher wrote:
Just don't need them. Never got around to using WiX only for patching so I
don't see any use for them.
There's nothing in WiX today that needs them, other than patching, but
that might change; there's lots of good info that's pre-digested in a
way that
On 18-May-12 11:32, Gareth wrote:
But you can install 64-bit dlls withoin a 32-bit package - they're just
files.
Not if they're marked as a 64-bit component that goes into a 64-bit part
of the file system. Then they're special.
then how can a 64-bit operating system interogate a bespoke file
On 18-May-12 15:53, Richard Mayes wrote:
Error 0x80004001: Unsupported registry key value type. Type = '7'
RegistrySearchValue failed: 'SOFTWARE\Microsoft\Microsoft SQL Server',
HRESULT 0x8000400
Like MSI, Burn doesn't support getting the value of a multi-sz string.
However, if all you want to
On 15-May-12 06:34, Pally Sandher wrote:
at
Microsoft.Tools.WindowsInstallerXml.Binder.BindDatabase(Output output, String
databaseFile) in e:\delivery\Dev\wix36_public\src\wix\Binder.cs:line 1582
Definitely a bug, please file. Workaround is to not suppress .wixpdb output.
--
On 15-May-12 10:53, Pally Sandher wrote:
Done -
https://sourceforge.net/tracker/?func=detailaid=3526942group_id=105970atid=642714
Thanks. Fixed for Monday's build. I am curious, however: Why do you
suppress .wixpdb generation? Is it a question of perf?
--
sig://boB
http://joyofsetup.com/
On 11-May-12 04:53, Gareth wrote:
Hi Bob, thanks for your input, but why would it ever be necessary to include
32-bit merge modules in a 64-bit package?
When you have a 64-bit component like a shell extension but everything
else is 32-bit. MSI doesn't support a 32-bit package with 64-bit
On 08-May-12 11:45, Gareth wrote:
Up until now I have been able to merge VC90 merge modules of both x86 and x64
varieties into the same package without any problem.
That's legal in an x64 package only.
--
sig://boB
http://joyofsetup.com/
On 07-May-12 09:51, Dmuller720 wrote:
But the question is still, can someone help me get a picture as the image
for a rectangular button?
Use @Bitmap=yes and @Text=Binary/@Id of bitmap.
--
sig://boB
http://joyofsetup.com/
On 02-May-12 11:51, Quinton Tormanen wrote:
The schema is 200, and when built back in 2010 using the same source
and toolset it worked up until the path validation.
Are you using the same OS on the build machine?
MSI (c) (88:6F): Note: 1: 2203 2: rmcwin.msi 3: -2147286779
MSI (c) (88:6F):
On 02-May-12 04:22, Kristjan Laane wrote:
I looked at the docs for the Product element and it is not clear to me from
this URL whether the Name property, for instance, is formatted or not:
It turns into the ProductName property, which cannot itself contain
property references.
--
sig://boB
On 04-May-12 16:00, Dmuller720 wrote:
I assume that the ImageSource attribute is what I want to use, but I am not
sure.
However, the ImageSource is not recognized and causes an error.
It's not part of any version of WiX I'm aware of. Where did you see it?
--
sig://boB
http://joyofsetup.com/
On 30-Apr-12 10:17, jean claude klodjan wrote:
- is it possible to generate abal:WixStandardBootstrapperApplication/
element, which would use a custom BA.dll ?
Yes. It's permitted under a BootstrapperApplicationRef element, so
you'll need a separate BootstrapperApplication for your custom BA.
On 30-Apr-12 11:10, Pally Sandher wrote:
Unfortunately still happens with 3.6.2328.0.
Heath's fix came in v3.6.2830.0.
--
sig://boB
http://joyofsetup.com/
--
Live Security Virtual Conference
Exclusive live event will
On 01-May-12 11:17, Rob Mensching wrote:
I bet you're using the WixUI and that has a custom action in it to verify
paths. You'll have to hack that out (basically, create your own UI) to get
it all to run on NT4.
See wix.chm on WIXUI_DONTVALIDATEPATH for how to skip validation.
--
sig://boB
On 28-Apr-12 17:03, Kristjan Laane wrote:
Thanks for the info Bob - but what determines whether a localized string is
formatted or not?
Whether it appears in a field that's documented as being formatted. Many
fields are but some are required to be string literals and aren't
formatted, so
On 01-May-12 19:18, Uma Harano wrote:
But the way I want it to work is as follows:
My media has a Setup.exe. At this level, I have a support folder that
contains the msi package that I want to bootstrap. So I want the Setup.exe to
launch the msi from this Support folder.
Burn doesn't work
On 01-May-12 16:34, Brian C wrote:
I have what appears to be a simple chained install using burn, where I
would like to do a RegistrySearch to read a key created by the first msi, and
use that to install the second msi to a subfolder of that location.
Burn doesn't support that today. All
On 28-Apr-12 16:07, Alexander Lamaison wrote:
I'm trying to create a custom no-UI bootstrap application by
subclassing CBalBaseBootstrapperApplication. It gets as far as my
OnStartup method but then hangs.
What are you doing in OnStartup? How are you calling Detect?
--
sig://boB
On 28-Apr-12 08:08, Alexander Lamaison wrote:
Is there a way round this? Can I easily compile the bootstrapper
application myself with VS 2005?
You'd have to do the same thing to all of Burn too.
--
sig://boB
http://joyofsetup.com/
On 28-Apr-12 07:20, Kristjan Laane wrote:
But I could not get the property to work as well: !(loc.Message_Foo) still
returns the static unevaluated string for me, being literally Foo blah blah
[Property1].
That means you're trying to use properties in a string that isn't formatted.
--
On 27-Apr-12 10:32, Pally Sandher wrote:
I'm quite happy to use the cutting edge (in some ways it's preferable) but I
get a little irked when things I've been led to believe are the standard ways
of doing things with Windows Installer by yourself other WiX
contributors/developers are
On 25-Apr-12 10:06, Pally Sandher wrote:
Why is it attempting to uninstall the patch when the condition is false the
patch has AllowRemoval=no?
Because Burn always attempts to uninstall a package that's present when
its install condition is false, and Burn doesn't know the patch is
On 25-Apr-12 11:45, Pally Sandher wrote:
Microsoft (R) Windows Installer Xml Linker version 3.6.2823.0
Copyright (C) Microsoft Corporation. All rights reserved.
light.exe(0,0): error LGHT0001: An item with the same key has already been
added.
On 22-Apr-12 17:06, Neil Sleightholm wrote:
That isn't the way it is coded,
I coded it, so I'm familiar. I didn't know about the support for a
license-less BA, so I didn't code for that possibility.
--
sig://boB
http://joyofsetup.com/
On 23-Apr-12 07:04, Pally Sandher wrote:
SuppressOptionsUI=yes hides the Options button. Cheers Bob (although if
there was documentation for BalExtension...).
There is, at least for WixStandardBootstrapperApplication Element (Bal
Extension). It doesn't seem to be getting on the Web site for
On 19-Apr-12 12:34, Pally Sandher wrote:
The bal:WixStandardBootstrapperApplication/@LicenseUrl attribute's value
cannot be an empty string. If you want the value to be null or empty, simply
remove the entire attribute.
The bal:WixStandardBootstrapperApplication element must have a value
On 01-Apr-12 16:56, Wesley Manning wrote:
I'm using WixStandardBootstrapperApplication.HyperlinkLicense and have
created a custom theme by modifying the hyperlinklicence theme xml file. I
found when I try to put an image inside the installPage element the
image is shown in the Modify
On 29-Mar-12 07:31, Kyle Lee wrote:
However, if I upgrade Office from Office 2003 to Office 2007 and then
perform the MSI upgrade, not only Word 2003 feature / Word 2007 feature
were installed, but also there are two entries (MyProduct v1.0 and
MyProduct v2.0) in ARP. If I tried to uninstall
On 01-Apr-12 05:57, Milan Kaše wrote:
Try to use PNG image format for the LogoFile instead of the ICO format.
Yep: LogoFile uses GDI+ to load the image and GDI+ doesn't support icons.
--
sig://boB
http://joyofsetup.com/
On 13-Mar-12 10:26, Dave Mateer wrote:
99.9% of the payload in my installer is the same between the various
languages.
The canonical way is to have one language-neutral installer and n
language-specific installers.
Is there any way to officially do this without duplicating the content? I
On 17-Feb-12 05:07, Tobias S wrote:
d) Is there a bug or is it not completely implemented ?
Yes, there are bugs, already filed.
--
sig://boB
http://joyofsetup.com/
--
Keep Your Developer Skills Current with
On 27-Feb-12 10:50, victorwhiskey wrote:
So is there a way I can define the font size and color for
title/subtitle/description...? and have all dialogs use that?
No, but you can use TextStyle to change font size and color.
--
sig://boB
http://joyofsetup.com/
On 27-Feb-12 11:29, Rob Mensching wrote:
I am not a lawyer so my comments cannot provide you legal advice but my
legally uneducated understanding of the license is that the output of the
tools is not OSS.
Of course, any use of a WiX extension or Burn includes code licensed
under the CPL...
--
On 27-Feb-12 15:57, David L. Beckwith wrote:
MyBA.exe WIN8=1
and
MsiProperty Name=WIN8 Value=
How do I get it into Value?
The command line is passed to the BA in the command
(BOOTSTRAPPER_COMMAND.wzCommandLine in C++).
--
sig://boB
http://joyofsetup.com/
On 10-Feb-12 12:03, David McCabe wrote:
I'm having a few problems with dark. The MSI I'm attempting to decompile was
built with WiX 3.5 and a modified form of WiXUI_InstallDir, by copying
WiXUI_InstallDir.wxs into aUI section and modifying:
Did you keep the WixUI_Mode property? The UI
On 15-Feb-12 10:15, Rob Mensching wrote:
File a bug, but I'm not exactly sure how to investigate. I'm (obviously)
not seeing the same problem. And if you're installing the WiX toolset,
then you aren't either (at least once).smile/
Both bugs involve per-user packages...
--
sig://boB
Please add that to the bug...
On 15-Feb-12 11:57, Peter Hull wrote:
I've done a bit of playing around and it seems to be linked to install
conditions, i.e. if I change my bundle's chain to
Chain
MsiPackage Id=one SourceFile=install.msi Compressed=yes
InstallCondition=
On 09-Feb-12 12:22, Sam Morris wrote:
doesn't replace any colons already in the Prefix attribute, so later on
the Binder gets confused when it splits the string on colon
characters...
Yep, not good.
I can file this as a bug if someone can add me to the project (sf
Anyone can file bugs.
--
On 06-Feb-12 17:08, Derrick Brown wrote:
[Show Dialog=InstallDirDlg
After=WelcomeDlg]UPGRADING_OLDER_PRODUCT AND NOT
INSTALL_LOCATION_FOUND[/Show]
You can't use Show for that; once the first modal dialog is shown, you
have to publish control events to manage the back/next flow.
--
On 06-Feb-12 06:44, Alexander Krivács Schrøder wrote:
I'm using the WiX v3.6 Beta (v3.6.2221.0) here. This functionality has worked
before, but now, the DetectMsiFeature event does not fire at all upon calling
Engine.Detect().
Did you set MsiPackage/@EnableFeatureSelection?
--
sig://boB
On 08-Feb-12 22:47, Grant Samuels wrote:
I noticed support has recently been added for the ExePackage/ExitCode
in order to provide some control in a reboot scenario, there is
currently no option for MsuPackage/ExitCode.
Because MSUs return standard exit codes:
On 07-Feb-12 10:29, Christian List wrote:
My first burn installer installs:
msi package A to location 1
msi package B to location 1
My second burn installer installs:
msi package A to location 2
That won't work: The product is already installed so Burn won't install
it again.
--
sig://boB
On 31-Jan-12 09:12, Alexander Lamaison wrote:
Is it possible to have a bootstrapper made with burn that doesn't show any UI?
The WixStdBA supports the /silent switch for no-UI installations.
--
sig://boB
http://joyofsetup.com/
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
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 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
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.
MsiProperty Name=ALLUSERS Value=1/
Right but if WiX, while building the bundle, thinks that all your
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 elevated rights.
What bug is that?
--
sig://boB
http://joyofsetup.com/
--
Try before you
On 25-Jan-12 21:52, Josh Suereth wrote:
Actually, I caught the pre-processor docs. Replacing every $ with $$
works. I just had to get my regex replacement correct. Sorry for the bum
email.
I think it's still a bug. $ introduces a preprocessor variable reference
but $$ should be necessary
On 26-Jan-12 15:02, DuBois, Joseph wrote:
Have aBundle which is installing severalMsiPackage(s) which we have set
theMsiProperty Name=ALLUSERS Value=1/ to load the individual packages
under all users, but it isn't installing the Bundle itself under ALLUSERS.
If your packages are all per-user
On 26-Jan-12 14:37, T. Kuro Kurosaka wrote:
I thought properties named with all uppercase letters are in
global effect, and passed between the server and the client, back and
forth.
It's one-way only, client to server. There's no way to set a property in
the server and have it available for
On 25-Jan-12 17:50, Andrew Collier wrote:
I'm trying to build a bootstrapper msi but I'm running into issues: Does
anyone know what I'm doing wrong?
Does it work if you use MSBuild? There's a bootstrapper project template
for Visual Studio.
--
sig://boB
http://joyofsetup.com/
On 25-Jan-12 03:37, Peter Bulyaki wrote:
One of the many requirements towards our installer is that
the bundle installer itself should not be a separately installed product -
only the MSIs.
See the Bundle element doc:
DisableRemove YesNoType wix_xsd_simple_type_yesnotype.htm Determines
On 25-Jan-12 11:46, Josh Suereth wrote:
I'm trying to bundle up Scala's documentation using WIX. Right now, the
light program is exiting with error LIGHT0083 that it can't find the files
I'm bundling. I have a file named Utility$$Escape$.html and it's
printing in the error message that its
On 25-Jan-12 04:15, Vadym Verba wrote:
Here is usecase: I have old v1.0 bundle installed and new patch bundle with
patches only (totally new bundle with new upgrade code or with the same
one?).
You'll have to do some additional work to associate the bundles. I
haven't done it, so I'm not sure
On 24-Jan-12 15:09, Paul Fazio wrote:
However, when I attempt to install I get the following error: Setup
failed while installing the MSIs. Unspecified error.
Where? The Burn log will have additional details, like an error code.
--
sig://boB
http://joyofsetup.com/
On 24-Jan-12 10:02, Vadym Verba wrote:
I have a small but a very vital question: how to patch bundle?
Build a new bundle that contains the patches, either by themselves or
with the original packages.
--
sig://boB
http://joyofsetup.com/
On 24-Jan-12 07:14, Peter Bulyaki wrote:
So I would rephrase my question: is there a way to install a bundle without
registering it not only in Programs and Features, but in general with
Windoes Installer as a separate product?
Bundles aren't MSI products. They need to run (and therefore be the
On 24-Jan-12 05:11, scott.lang...@appsense.com wrote:
I invoked MSBuild with the build project command from within the VS2010 IDE.
The Sign* targets don't run by default. Set the SignOutput property to
true and call the Signing target.
--
sig://boB
http://joyofsetup.com/
On 23-Jan-12 10:29, scott.lang...@appsense.com wrote:
And tried to override the Signxxx targets, but as far as I can tell, they
don't get called.
How did you invoke MSBuild?
--
sig://boB
http://joyofsetup.com/
--
On 23-Jan-12 05:36, Peter Bulyaki wrote:
I am not allowed to comment on the bug so should I file this as a new one?
I re-opened it; please add your results.
--
sig://boB
http://joyofsetup.com/
--
Keep Your Developer
On 23-Jan-12 10:17, Dirk Kuypers wrote:
I am just facing a similar problem like described in the ticket above.
See http://www.joyofsetup.com/2010/10/09/experimental-results-part-ii/.
--
sig://boB
http://joyofsetup.com/
On 21-Jan-12 23:48, Sunny Li wrote:
Just tried out the weekly build 3.6.2520, I think there is a bug in the
wix.ca.targets.
Please file a bug.
--
sig://boB
http://joyofsetup.com/
--
Try before you buy = See our
On 17-Jan-12 17:16, Peter Hull wrote:
I'd still like to hear if anyone has any comments on a per-user
install which includes a device driver - is it always better to do it
per-machine.
Drivers are per-machine resources so a per-user installer that includes
one can't offer the benefits of
On 17-Jan-12 05:58, Per Næsgaard Andersen wrote:
[Mixed Platforms/Debug] [some
path]\Fls.Xxx.Install\Fls.Xxx.Install.wxs(58,0): error LGHT1056: The Property
table contains a row with primary key(s) 'MsiHiddenProperties' which cannot
be merged from the merge module '[some
On 13-Jan-12 01:41, Peter Hull wrote:
Bob: would it be possible to have the burn engine signed (by Microsoft) in
the released WiX 3.6
That would mean that the UAC prompt would show Microsoft as the owner of
your bundle.
or have an option to specify the burn engine in the .wxs file - as I
On 13-Jan-12 12:20, Schley Andrew Kutz wrote:
My WiX installer removes the VC10 redistributable merge modules on upgrade.
Merge modules aren't atomic; their contents are mixed into the .msi. In
this case, you're running into a known bug in MSI in how it deals with
assemblies:
On 12-Jan-12 12:52, John Cooper wrote:
Bug is 3473007.
Thanks; I'll take a look.
--
sig://boB
http://joyofsetup.com/
--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
On 14-Jan-12 13:00, Ulrich Proeller wrote:
When calling Pyro with more than one .mst file, I get an error message
Additional argument 'Setup_DE_2.0.0.0.wixmst' was unexpected.
Can Pyro currently take more than one transformation or not?
Yes it can. What command line are you trying?
--
On 10-Jan-12 17:48, John Cooper wrote:
Test NVPPTb.SetEditNetTcpBinding.Header failed with unknown operation.
That's bad. But thanks for the repro! Can you file a bug on SF?
--
sig://boB
http://joyofsetup.com/
--
On 12-Jan-12 05:47, Nick Ball wrote:
I haven't started using burn yet - but I'd like to - and signing will be an
issue for us. At the moment, I hand an unsigned MSI over to the release
manager for signing. He is the only person with access to the certificate.
Can we still do this with burn?
On 11-Jan-12 03:00, Ulrich Proeller wrote:
The switch -sf in the pyro command was added the get rid of a duplicate key
error.
That's likely the root cause of your problem. Fix the underlying bug
before trying workarounds.
--
sig://boB
http://joyofsetup.com/
On 05-Jan-12 16:33, Hoover, Jacob wrote:
Is there a way of informing an end user that a patch is not valid (due
to a newer patch all ready being applied)?
Check patch applicability. That's what Burn does. The 1.0.2 MSP won't be
applicable to a 1.0.3 product.
--
sig://boB
On 06-Jan-12 16:58, Daniel Sniderman wrote:
These are SQL Server related DLL's - so I can't assume they will be on the
GAC of the target machine - and I'd like to simply continue to include them
as files in the MSI - i.e. I don't want to GAC them on the target machine.
You probably don't
On 05-Jan-12 09:05, Bruce Cran wrote:
From a verbose install log I see that MainEngineThread is returning
ERROR_SUCCESS_REBOOT_REQUIRED (3010) - I wonder if WI only checks for
ERROR_SUCCESS when determining if it should refresh the list, or not
the other ERROR_SUCCESS_* values? If so, would
On 04-Jan-12 10:30, Scharp, Craig wrote:
I have a MSI with several dialogs including a choice of features. It is
elevating privileges correctly (showing the UAC Popup) for my deferred
actions, but I can't seem to get it to popup before the welcome dialog.
MSI doesn't support elevated UI or
On 03-Jan-12 12:28, Alan Goode wrote:
Thanks for the reply Rob,, but could you be a little more specific? Does
that mean that I need to connect to source control using TortoiseSVN and
download the source from there?
If you just want to look at the source (and not build it), use the
sources
On 03-Jan-12 10:07, abgrallyann...@free.fr wrote:
I'm working with Wix 3.6, Installation goes well, but I've an issue when I
try to uninstall.
My detection process allows users to install (if package is absent) or
uninstall( if package is present). After the uninstallation, I launch my
On 03-Jan-12 17:15, Robert Brunhuber wrote:
more time in debugging (the loading of) my wizard, I'd like to know if
these wizards are supported in votive, or if anyone succeeded in
creating one.
Votive uses MPF so inherits its support for wizards but doesn't add
anything of its own.
--
On 30-Dec-11 10:46, David P. Romig, Sr. wrote:
How can I prevent the installer from raising the MsiRMFilesInUse dialog
and always select Do not close the applications without user
interaction?
See Using Windows Installer with Restart Manager in the MSI SDK.
--
sig://boB
http://joyofsetup.com/
On 27-Dec-11 13:51, Jacob Langston wrote:
I am unable to specify PropertyRef except under a fragment node. Is there
a way to do the following in the bundle node?
PropertyRef Id=NETFRAMEWORK35/
No. Those checks rely on running inside an MSI package, which isn't the
case for a bundle.
On 22-Dec-11 16:21, John Cooper wrote:
In partial answer to my own post, it appears that the Value attribute can be
formatted for Property Value Tests, but cannot be formatted for Multi-Value
Property Tests and Name-Value Pair Property Tests. Would be nice to allow
formatted values for
On 27-Dec-11 07:47, Neils Christoffersen wrote:
I compile and install, but my custom message doesn't show up. It's
still Copying new files. Am I missing something?
You need to add a UIRef Id=WixUI_ErrorProgressText / to pull in the
default authoring, which you can then override.
--
sig://boB
On 22-Dec-11 08:23, Stelios Kyprou wrote:
Ok it seems that Remove=ALL was not set for the following reason:
One of the features had a conditional installation, as following:
http://www.joyofsetup.com/2008/05/16/make-sure-features-are-always-enabled-so-they-can-be-removed/
--
sig://boB
On 12-Dec-11 07:43, Francois Human wrote:
Where can I find documentation or a tutorial on how to use the Clickthrough
Project?
ClickThrough is currently unsupported. It will come back in a new form
in a future version of WiX.
--
sig://boB
http://joyofsetup.com/
On 14-Dec-11 16:01, Sunny Li wrote:
[0AFC:05D0][2011-12-14T15:53:26]: Error 0x80004005: Failed to open
container: WixAttachedContainer.
Known bug that's been fixed for the next build.
--
sig://boB
http://joyofsetup.com/
On 14-Dec-11 02:52, Toru Takeguchi wrote:
pyro -delta .\v1.3.0\patch.wixmsp -out .\v1.3.0\Product.msp -t RTM
.\v1.3.0\Diff-v1.2.0.wixmst -t RTM .\v1.3.0\Diff-v1.1.0.wixmst
pyro.exe : error PYRO0001 : The specified arguments are not within the range
of valid values
parameta managed
Exception
On 13-Dec-11 21:25, Sunny Li wrote:
Is there anyway to turn off the verbose logging for the MSI's included in
the WiX bundle?
No.
If not, is there anyway we can log the msi errors into the bundle log?
MSI doesn't support that.
--
sig://boB
http://joyofsetup.com/
On 13-Dec-11 19:17, Ian Williams wrote:
Is there any way I can keep the standard bootstrapper and get something like
selectable items?
No, WixStdBA doesn't support feature selection.
I've looked at http://wix.sourceforge.net/manual-wix3/wixstdba_intro.htm, but
the completely customizing
On 10-Dec-11 13:43, Roy Chastain wrote:
Is there a mechanism to employ a custom detection in the Burn
ManagedBootstrapperApplication that would affect the install/no install
status of an ExePackage?
OnPlanPackageBegin lets you change the request state.
--
sig://boB
http://joyofsetup.com/
On 08-Dec-11 02:09, Nevskiy, Alexander wrote:
On executing light.exe I got the following error:
error LGHT0094 : Unresolved reference to symbol
'CustomAction:[CustomSerialValidateProp]' in section
'Product:{3E8964C7-5FA5-4740-A3D6-191E2043963C}'
According to
On 07-Dec-11 16:19, Brad Wildenborg wrote:
and am using NAnt 0.91. I'm mostly just after getting access to the Burn
utility, so if anyone could help me get it built or link to where I could
download a prebuilt version, that would be wonderful.
It's part of every WiX v3.6 build: x86\burn.exe.
On 06-Dec-11 12:35, Gary Gocek wrote:
Is it correct to say that if LIGHT is allowed to run the internal
consistency evaluators (ICEs, light runs them by default), and if NIT is
used to run unit tests, that the account performing these actions requires
admin rights? (WIX 3.5, Windows Server
On 07-Dec-11 11:29, Robert Hermann wrote:
Anybody have any ideas
Use Orca to look at the ControlEvent table.
--
sig://boB
http://joyofsetup.com/
--
Learn Windows Azure Live! Tuesday, Dec 13, 2011
Microsoft is
On 22-Nov-11 03:18, ppremk wrote:
2. How to launch a payload file (exe) after installing running the
bootstrapper? I am using my own custom theme file and noticed that there is
a launch button, I am not sure how to include a launch condition into that
section.
Create a Variable named
On 18-Nov-11 05:26, Michael Stoll wrote:
is it possible to enable/create a ICMP Firewall exception using
WixFirewallExtension?
No, that's not supported.
--
sig://boB
http://joyofsetup.com/
--
All the data
On 13-Nov-11 19:38, Keith Moore wrote:
This dialog will result in an empty ComboBox list because theControl
property is referencing indirectly but in theComboBox element I have no
way of dereferencing it. Is this a bug or is there some syntax of which I am
not aware?
Looking at the MSI
301 - 400 of 4150 matches
Mail list logo