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
12 matches
Mail list logo
