for wix v3, build 3419, why is there a difference in the wix.dll that is
installed with the msi and the version found in the zip file?
if i install the msi to get the votive stuff and the xml references and
stuff installed for VS, but then use binaries extracted into a temp
directory to compile
processor, and execute the start command which
has the option /D to specifiy the current dir.
Rene
--
*From:* [EMAIL PROTECTED] on behalf of koawmfot
*Sent:* Thu 8/23/2007 21:55
*To:* wix-users@lists.sourceforge.net
*Subject:* [WiX-users] WixShellExec CAQuietExec
processor, and execute the start command which
has the option /D to specifiy the current dir.
Rene
--
*From:* [EMAIL PROTECTED] on behalf of koawmfot
*Sent:* Thu 8/23/2007 21:55
*To:* wix-users@lists.sourceforge.net
*Subject:* [WiX-users] WixShellExec CAQuietExec
I need to lauch an executable at the end of my installation. currently i
use the CAQuietExec function and launch the executable with its parameters
and it is fine. the problem is that the command i execute creates a result
text file. the file is supposed to be created in the application's
searching around i found that the -gg switch when passed to heat generates
GUIDs for each component. this is a very nice little feature, and i wonder
why it is undocumented with the /?.
i was wondering if there are other undocumented switches for heat, as well
as undocumented switches for the
on this one.
also, would this be two bugs or one if i were to file, and is this a bug in
the documentation, or the compiler?
thanks
doug
On 7/28/07, Bob Arnson [EMAIL PROTECTED] wrote:
koawmfot wrote:
i need to advertise a ffew file extensions so that self repair can
kick off for some
i need to advertise a ffew file extensions so that self repair can kick off
for some specific HKCU registry keys. the problem i have is that i am only
adding an extension element and a MIME element, but no verb element, and
that leaves the verb table out of the final MSI. now if i try and
microsoft provides an msm for MDAC, and the instructions on how to update
it, here: http://support.microsoft.com/kb/320788. i atcually used that, and
converted to a wixlib, and was hoping to do the same for JET.
i was wondering if anyone had anything similar for JET 4.0 SP8. i know
there are
The infor below was posted on the mail list:
Re: [WiX-users] WiX 3.0 wixca.dll QtExec
Erlichmen, Shay
Wed, 21 Feb 2007 03:51:59 -0800
There is a documentation mistake in WiX3 chm, you need to replace the
Id=wixca with Id=WixCA and remove the Binary element.
Then you will need to add
using v3.0.2911.0 i had no problem with the WixUtilExtension and
ServiceConfig element. I just installed v3.0.3001.0 and now my msi dies
when it gets to SchedServiceConfig. below is the relevent MSI log file
information:
Action start 13:26:37: SchedServiceConfig.
MSI (s) (10!38)
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
}\Version
2.0 mscomctl.ocx
regA880A414284125A06201F7DBCBAAA4E4 0
CLSID\{1EFB6596-857C-11D1-B16A-00C0F0283628}\VersionIndependentProgID
MSComctlLib.TabStrip mscomctl.ocx
On 5/2/07, Bob Arnson [EMAIL PROTECTED] wrote:
koawmfot wrote:
Which version of WiX are you using? I believe that was changed
[EMAIL PROTECTED] wrote:
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.g WiX v3 added the concept of
binary .wixlibs that can contain the files they ship, so
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
14 matches
Mail list logo