The setup template did change a bit in 3.6. They put the directories and
components into separate fragments. And they added the MediaTemplate element
and added the Directory attribute to the ComponentGroup. But for the most
part, it's mostly like version 3.5, or version 3.0 for that matter.
Fragm
Hello everyone,
I'm just getting started using version 3.6 (latest build) and I'm having a hard
time understanding the basics. The main reason is, that it seems that there's
very few to none documentation available. I've started reading the book and
also the tutorial, but they are very differen
Looking at the definition for ServiceInstall, you have to have the File
element in the same component. So, that limits you. Otherwise you'd be able
to put the File in one component and maybe reference it by two different
ServiceInstalls. Alas.
I've done something that may be similar to what you're
What does DiskPrompt and VolumeLabel mean when used on a MediaTemplate
element? On the old Media element, it made sense because each Media element
corresponded to a unique CAB file:
But the MediaTemplate makes the cabinets for us and there's only one
element. What does it do with to have these
On 12/07/2012 23:40, Darwin Baines wrote:
> So having done this, and gotten it to work I'm at the stage of wondering what
> would be the ramification if we were to distribute it with our product and if
> it will be a common problem with others.
I think this is something you'd need to ask a lawye
Thanks for answering! If a quiet bootstrapper is what you want, take a look at
writing a custom one. You have total control over every aspect of the UI so you
can show as little or as much as you like.
There's not a lot of documentation, but the WiX bootstrapper itself is very
well done and was
I may have taken the wrong approach and this may become a non-issue once the
documentation comes out and clears things up, but I was looking to make a quiet
bootstrapper whose only dialog was the "usage" help page; kind of an
incremental step from a straight MSI to a bootstrapper, where the MSI
Out of pure curiosity, why would you need to do your own custom bootstrapper?
The WiX Burn bootstrapper is incredibly flexible and allows you to completely
control everything I can imagine anyone would need. What does Burn not do that
you need?
Thanks for satisfying my curiosity.
John
Co-fo
Don Walker wrote
>
> Here is the situation:
>
> 1. We allow multiple versions of our product to be installed at the same
> time if they have a different Major.Minor version. I don't believe that
> the MajorUpgrade element supports this option. The UpgradeVersion elements
> shown should provide f
Is it possible to use the ServiceInstall element and install multiple Windows
Services using a single host.exe file? If so, how?
This works for a single service, but I cannot install the same file to the same
directory from two different components...ICE30 error.
I am looking into possibility of creating my own bootstrapper that tweaks the
standard bootstrapper.
I assume that if I write my bootstrapper from scratch, I shouldn't run into
complications, but if I start with the standard bootstrapper code and make some
changes that fits my situation, I've c
Rob,
Unless I am mistaken, that criteria: "[no] Property substitutions ..." is
only relevant if I am asking WiX to generate the Guid; which seems to be
indicated in the initial message.
"The Component/@Guid attribute's value '*' is not valid for this
component..."
What has me confused is that th
I find 3.6 very stable.
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Thursday, July 12, 2012 11:49 AM
To: General discussion for Windows Installer XML toolset.
(wix-users@lists.sourceforge.net)
Subject: [WiX-users] Status of WiX v3.6 Releas
Rob Mensching-7 wrote
>
> Or use MajorUpgrade element.
>
I don't think that the MajorUpgrade element gives me the flexibility that I
need. My assumptions (and what I believe to be best practice) are:
1. The UpgradeCode is fixed for all versions of the product.
2. The Product Id is set to "*"
WiX v3.6 RC0 was announced on 4/3/2012 and WiX v3.6 RC was announced on
5/28/2012.
Does anybody have any guess as to how close we might be to WiX v3.6 RTM?
Hmm... let me ask a different question. We are not using burn yet and I
understand most of the work right now revolves around burn. Would u
Or use MajorUpgrade element.
On Wed, Jul 11, 2012 at 12:36 PM, Don Walker wrote:
>
> Chad Petersen wrote
> >
> > I was able to get past this error in your example by adding this inside
> > the Fragment
> >
> >
> >
> >
> >
>
> Scheduling RemoveExistingProducts worked for me too. Ironica
This part of the error message is pertinent: "[no] Property substitutions
as the key path"
On Wed, Jul 11, 2012 at 12:36 PM, Bill Packard wrote:
> WiX 3.0.5419, VS 2008.
> Attempting to convert merge modules (only used internally) to wixlib.
> Almost there, but have encountered a set of errors th
17 matches
Mail list logo
