Hi Bob,
I can't say I fully agree with you (or maybe there is a misunderstanding on
my part), because in my understanding the bundle is just a proxy that
installs multiple MSI products - each of which can be uninstalled
individually. One of the many requirements towards our installer is that
the
On 24/01/2012 16:46, Parkes, Kevin wrote:
The only snag is having the checkbox at the bottom of the dialog to overcome
the problem of its having a grey background - it there a way to get the
checkbox in the main bit of the dialog without the grey background?
Yes, but it's a bit hacky. You
Found Paraffin!
http://www.wintellect.com/CS/blogs/jrobbins/archive/2010/08/31/zen-of-paraffin.aspx
I think that this is what I need! So that my HEAT won't generate different
GUIDs each time.
Are you familiar with it?
-Original Message-
From: Peter Shirtcliffe
I'm not sure, if I understood this right.
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?). I installed patch bundle and then decided to change/repair/uninstall
some patched product from v1.0
No. The recommendation is to use heat to generate your first version and then
make the changes manually thereafter. Our product and work practices make
this a suitable way to work. We use * for component guids to keep them
constant.
We have one product that heats files with each build but we
I would concur. Saving as much configuration to a database as possible, and
deferring as much configuration as possible to application configuration, is
the most stable approach. We use this on all of our products. The installer
modifies the web.config only enough to bootstrap the
Thanks! I've been thinking about splitting this into two files so I'll explore
this further.
RMartin
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Christopher Painter chr...@iswix.com
Date: Tue, 24 Jan 2012 14:26:10
To: General discussion for Windows Installer XML
http://robmensching.com/blog/posts/2010/8/2/The-first-thing-I-do-with-an-MSI-log
Thanks Rob, probably the most useful piece of info I've heard regarding MSI's.
I knew about the logs but not value 3.
Cheers,
James
LEGAL NOTICE
This message is intended for the use of the named recipient(s) only
Hi everyone!
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 source path is
The best way to do this is to ask yourself (or whoever made the decision)
whether you really need multiple versions for customers. In most situations
you should be able to get away with just one installer and if you really need
to, allow some parts of it to be optional to the end user.
If this is
Are these problems in 3.5 or 3.6? Last year I discovered a defect in DTF
wherein a race condition upon completion of a DTF custom action call would
cause a failure return to Windows Installer, even when the managed code
custom action itself returned success. That was fixed in 3.6, but the bug
Blair,
That is excellent information. Yes, I am on 3.5 currently. I'm no longer
with Overwatch so I can make the call to go to 3.6 much easier.
FWIW, in this install I have 1 immed. DTF CA that costs and then 2 more
CA's that perform uninstall and install actions. The cost CA always
As Chris said excellent information. Mine problem was with 3.5 and this ties in
with what I was seeing; on my VMs running on an i7 host I never saw the problem
but the tester often got it on his lower powered host. He need move to a VM on
an ESX host and the problem largely went away. I think I
I tried creating a payload for the dependency files. I just can't figure out
how to store them in the correct subdirectory. It seems they are all stored
in the same directory as the setup.exe
[My3rdPartyInstaller]
|..[1033_XXX_XX]
|.[]
|..[directory1]
|.[]
|..[directory2]
|.[]
I'm going to be creating a trojan installer that serves as a health check
and deploying it daily to 2200 machines. I'll be able to stress test the
fix made in 3.6 and see what happen.s
From: Neil Sleightholm n...@x2systems.com
Sent: Wednesday, January
Nvm, I forgot to put the Name attribute.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-ExePackage-that-depends-on-many-files-tp7205293p7224976.html
Sent from the wix-users mailing list archive at Nabble.com.
I'm working for a company that's currently overhauling its evaluation process,
and one of the things we're trying to do is combine our 32- and 64-bit MSI
installers into one package. I saw that on stack overflow
No. MSI can only support one architecture per script as far as I know.
You still need a bootstrapper to launch the appropriate installer.
Dieter Lunn
http://ubiety.ca
On Wed, Jan 25, 2012 at 2:40 PM, Malcolm D. McCrimmon
malco...@windward.net wrote:
I'm working for a company that's currently
I'm trying to build a bootstrapper msi but I'm running into issues: Does anyone
know what I'm doing wrong?
*Source:*
?xml version=1.0 ?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Bundle Name=MSI Bundle Version=1.0.0.0 Manufacturer=TEST
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/
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.
- Josh
On Wed, Jan 25, 2012 at 9:36 PM, Bob Arnson b...@joyofsetup.com wrote:
On 25-Jan-12 11:46, Josh Suereth wrote:
I'm trying to bundle
Except for that one repeatable machine, the problem always went away upon
retry (the same behavior you all have reported). That one machine was able
to repro more than once in a row, and after about four days I even got it to
repro in the debugger. That's when I finally discovered exactly what was
Hi,
I'm just curious what can burn and netfx protocols supports? I need to
install SQLServer Express with my bundle I would like to see the progress
bar moves while it is installing instead of installing in the background. It
may look like that the installer hangs and doing nothing.
Tried both
27 matches
Mail list logo
