@lists.sourceforge.net
> Date: Thu, 8 Aug 2013 21:05:55 +
> Subject: Re: [WiX-users] wixlib backward compatibility in WiX 3.5, 3.6, 3.7
>
> I have used wixlibs on WiX 3.5 and WiX 3.6 projects. My experience is that a
> Wix 3.5 built wixlib will work with WiX 3.6 projects, but
913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: Michael Turner [mailto:mcturner...@gmail.com]
Sent: Thursday, August 08, 2013 3:58 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] wixlib backward compatibility in WiX 3.5, 3.6, 3.7
Doe
Does anyone have experience using 3.5-built wixlibs with light.exe in WiX 3.6
and 3.7? For purposes of this discussion, I'm only concerned with the
official RTMs (3.5.2519.0, 3.6.3303.0, 3.7.1224.0).
My objective is to use wixlibs for inter-project collaboration, so that one
project can produce w
product core, with outside pieces.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: February-21-2013 2:20 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLib not behaving as desired
Did you have a Property in the Fragment
gt; >
> > NOT
> > Installed
> >
> >
> > NOT
> > Installed
> >
> >
> >
> > I have 15 or so prerequisite fragments and a binary fragment within
> > the same file.
> >
> > -Original Message-
>
: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLib not behaving as desired
I think use of PropertyRef is awesome in that case. If you didn't have the
Condition (which uses the Property) I might consider using CustomActionRef
instead. But I like PropertyR
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Wednesday, February 20, 2013 3:27 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] WixLib not behaving as desired
>
> I've yet to see a c
.
Subject: Re: [WiX-users] WixLib not behaving as desired
I've yet to see a case where real content didn't exist in a Fragment that could
be referenced.
On Wed, Feb 20, 2013 at 1:12 PM, Hoover, Jacob
wrote:
> This smells like a need for a FragmentRef, which I currently work
&g
Mensching [mailto:r...@robmensching.com]
> Sent: February-20-2013 4:01 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] WixLib not behaving as desired
>
> If references are broken, the linker would tell you it couldn't find a
>
@robmensching.com]
> Sent: Wednesday, February 20, 2013 3:01 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] WixLib not behaving as desired
>
> If references are broken, the linker would tell you it couldn't find a
> symbol. I think yo
?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: February-20-2013 4:01 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLib not behaving as desired
If references are broken, the linker would tell you it couldn't find a
symb
so I don't know if that is
possible.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, February 20, 2013 3:01 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLib not behaving as desired
If references
rectory section.
> How do I know if the references are not broken?
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: February-20-2013 3:28 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] WixLib not beha
Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLib not behaving as desired
References flow from the Product element down. Follow your references.
There isn't enough below to really know what is wrong.
On Wed, Feb 20, 2013 at 12:20 PM, Marc Beaudry wrote:
> Hopefully this
Y]MyBinary.exe"
> WorkingDirectory='APPLICATIONROOTDIRECTORY' >
> SourceFile="SomeIconFile.ico"
> />
>
> Key="Software\Microsoft\[Manufacturer]\[ProductName]" Name=&qu
: February-20-2013 3:04 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixLib not behaving as desired
It all depends on what is in your Fragments and what is referencing what.
My guess is by moving the Shortcut, you removed the reference to oen or more
Fragme
I have a lib file that contains a bunch of files and a desktop shortcut to
one of the binaries. I then have my (product.wxs) main installation XML
file. My project has a reference to the lib file. It all compiles and links
perfectly. (My MSI is perfectly functional at this point)
BUT:
If
It all depends on what is in your Fragments and what is referencing what.
My guess is by moving the Shortcut, you removed the reference to oen or
more Fragments in you .wixlib.
On Wed, Feb 20, 2013 at 12:00 PM, Marc Beaudry wrote:
> I have a lib file that contains a bunch of files and a desktop
. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Monday, May 17, 2010 5:44 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] wixlib
"The only thing I would add to that is that you need to add a "ref" to the
fragments that you want to inclu
serv.com
Please consider the environment before printing this e-mail
> -Original Message-
> From: Kurt Jensen [mailto:kurt.jen...@ophir-spiricon.com]
> Sent: Monday, May 17, 2010 4:00 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-user
: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] wixlib
I assume that you found the "Adding WiX References" topic in the WiX help:
http://wix.sourceforge.net/manual-wix3/votive_wix_references.htm
The only thing I would add to that is that you need to add
lease consider the environment before printing this e-mail
> -Original Message-
> From: Kurt Jensen [mailto:kurt.jen...@ophir-spiricon.com]
> Sent: Monday, May 17, 2010 3:11 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] wixlib
>
&
I'm trying to understand wixlib. I've spent an hour searching do, web,
and archives.
After I create a wixlib, how do I include it in my installation?
Kurt Jensen
**
This email and any files transmitted with it are confidential
eric.hyb...@emc.com wrote:
> I'm not sure if this is as-designed or not, but it turns out the problem
> was in having multiple fragments in the wixlib source, and no reference
> between the fragments.
>
Yes, that's by design. You can add references and keep the fragments
small, which has the
I'm not sure if this is as-designed or not, but it turns out the problem
was in having multiple fragments in the wixlib source, and no reference
between the fragments.
This doesn't include the CustomAction or InstallExecuteSequence updates,
but it does include the Component and ComponentGroup
Can you share out an example of how the elements are organized in Fragments?
Most likely you're just needing a reference that isn't in place.
On Tue, Dec 22, 2009 at 3:33 PM, wrote:
> I defined some components and custom actions and use those custom
> actions in the InstallExecute sequence withi
I defined some components and custom actions and use those custom
actions in the InstallExecute sequence within a Fragment. When I create
a wixlib (with lit.exe) from that Fragment and include the .wixlib with
my primary msi light command line, I get the components, but not the
custom actions or th
Sent: 06 July 2009 18:38
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] wixlib and media/diskid settings
What about using an XSL transform to modify the heat output?
Nick Ball wrote:
> Hi,
>
>
>
> I'm creating a wixlib, and then using it in
Hey Nick,
Have you looked into a custom heat.exe extension? You would only have to
create a mutator that added the disk Id of your choice. It would also give
you the ablitity to do some more advanced manipulation.
http://blogs.msdn.com/icumove/archive/2009/07/02/WiX-Heat-Extension_3A00_-Setting-U
What about using an XSL transform to modify the heat output?
Nick Ball wrote:
> Hi,
>
>
>
> I'm creating a wixlib, and then using it in my main setup program, but
> I'd like the lib to go into a separate cab file. Because the contents of
> the lib have been generated by heat, I've put the disk ID
Hi,
I'm creating a wixlib, and then using it in my main setup program, but
I'd like the lib to go into a separate cab file. Because the contents of
the lib have been generated by heat, I've put the disk ID on the
directory, rather than each component. This code, understandably, does
not work:
values.
Kindly help me ASAP. I hope I am clear in what is needed.
Thanks
From: Bob Arnson [...@joyofsetup.com]
Sent: Tuesday, December 23, 2008 5:36 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiXLib - Including some
Required" Component Group. It'll all stitch
back together.
-Original Message-
From: Drew Turner [mailto:dr...@pandell.com]
Sent: Monday, December 22, 2008 14:59
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WiXLib - Including some or all components.
Hello,
We have
Drew Turner wrote:
> This approach works great for the scenario when we want to include the
> entire set of binaries. Although it seems to fall down when we only
> want to include certain components. For example say I only wanted to
> include the RequiredBinary for a certain project. I was wonde
Hello,
We have recently updated our solution from using a Merge Module to
utilize a WiX library. Right now the library is used to include a set
of binaries in other projects. Basically there is a DirectoryRef that
contains a of the component consisting of the (dll, pdb and xml files).
Then th
ching will
have something more descriptive to go on in the subject.
-Dave T.
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2008 4:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiXLib installed files not be
David Terrell wrote:
> However, upon uninstall only the files/keys listed in the main MSI's XML are
> uninstalled, while the WiXLib's files/keys are left behind.
Get a verbose log on uninstall and check around the InstallValidate
action to see the actions MSI is taking for the component. MSI l
I've created a very simple installer to test some things. In this case, we
deploy 32-bit and 64-bit assemblies that are very similar. I thought it would
be easiest to make a WixLib project, write the logic to get the assemblies
based on the Platform. This has so far worked very well. I refer
Hello,
Using a works, I'm gonna file a bug report for this
"!(wix.id)", I had to rename the Id though so it would not conflict
with the existing default [ProductName] property.
Thanks for the help,
Kind regards,
Wouter
2008/6/17 Bob Arnson <[EMAIL PROTECTED]>:
> Wouter Demuynck wrote:
>>
Wouter Demuynck wrote:
>
> http://schemas.microsoft.com/wix/2006/wi";>
>
>
>
>
>
>
One possibility is that the !(wix.id) uses aren't enough to reference
the WixVariable definitions in the library. Try this: Add a Property to
the li
Yes, I am getting the following error:
The WiX variable !(wix.ProductName) is unknown. Please ensure the
variable is declared on the command line for light.exe, via a
WixVariable element, or inline using the syntax !(wix.ProductName=some
value which doesn't contain parenthesis).
I'm using the pr
Wouter Demuynck wrote:
> Is it possible to define WixVariables inside a Fragment in a .wixlib, then
> import the library in an MSI project via project references and access these
> variables?
Yes. Are you getting errors doing so?
--
sig://boB
http://joyofsetup.com/
--
Hello all,
Is it possible to define WixVariables inside a Fragment in a .wixlib, then
import the library in an MSI project via project references and access these
variables? I have been trying to accomplish this to avoid having to maintain
the same set of variables twice. I'm using the latest wee
koawmfot wrote:
> so the question is, is this a bug or is this by design. bob had
> mentioned that this was something that should not be in this version
> and was already remedied.
I was misremembering -- that was related to services, I believe.
> i test weather i captured all the correct regi
erefore isn't fooled by spaces in
paths.
--
Mike Dimmick
--
*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *koawmfot
*Sent:* 02 May 2007 16:49
*To:* Bob Arnson
*Cc:* wix-users@lists.sourceforge.net
*Subject:* Re: [WiX-users] wixlib and extensions and msm&
May 2007 16:49
To: Bob Arnson
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] wixlib and extensions and msm's
sure...
the file in this example is mscomctl.ocx (i figured if you wanted to
reproduce, it would be an eas
sure...
the file in this example is mscomctl.ocx (i figured if you wanted to
reproduce, it would be an easy file to get...)
this is the snippet of code:
and that gives me this, take
koawmfot wrote:
Which version of WiX are you using? I believe that was changed
sometime recently to not quote.
I am using v3.00.2813. i believe that is the last release.
Hmmm...Can you post the WiX authoring and the resulting Registry rows?
--
sig://boB
http://joyofsetup.com/
---
thanks for your help bob...
On 5/2/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
Light is a "smart" linker; it links in only the sections that are
referenced. A "section" is a Product, Module, or Fragment (and probably
Patch and PatchCreation, just to be pedantic). You can break up your
authoring
koawmfot wrote:
1. I have authored a large file containing maybe 50 vbcontrols
(ocx, dll) and compiled it into a master binary wixlib containing
the files. My goal was to reference components from this master
file when i needed specific ones in a main project. The problem
i
ok.. perfect answer and that is what i thought...
so that set me on my path and leaves me know with a few other questions, one
related to the topic and a few slightly off-topic... i am using only wix
v3.
1. I have authored a large file containing maybe 50 vbcontrols (ocx, dll)
and compiled it
koawmfot wrote:
> well, technically it isn't really a bug if the v2 difxapp.wixlib has
> different elements and schema references than it should in v3.
True -- I'm not saying it'll get fixed. WiX v3 added the concept of
"binary .wixlibs" that can contain the files they ship, so they're full
re
well, technically it isn't really a bug if the v2 difxapp.wixlib has
different elements and schema references than it should in v3. it is really
just not an ap to date wixlib. unless what you are saying is that the
WixDifxAppExtension.dll contains the v2 wixlib and that is why i need to
provided
koawmfot wrote:
> so my question is, is the difxapp extension just not ready yet or am i
> doing something wrong? the final msi worked as it should.
Correct -- DifxApp itself doesn't ship with WiX v3. There's an open bug
right now that WiX v3 can't consume the WiX v2 Difx .wixlib.
--
sig://bo
In a previous message this was posted:
Re: [WiX-users] Question about upgrading to Wix3 (beta)
Bob Arnson
Sun, 25 Feb 2007 11:57:39 -0800
James Hill wrote:
So, my question is why are there no .wixlib and .wxl files in the Wix
3.0 beta distribution.
They're included in the WiX extensions. So
55 matches
Mail list logo
