That's an experimental extension some of us have been
working on for a while for HTML Help integration support(it will be rolled
into the VSExtension very soon). You can hand-modify dark.exe.config to
remove "WixHelpExtension" and a semi-colon, and it should work. Sorry for
the
You indicated a problem running light but the error message
includes "CNDL" which indicates an error in candle. What version of wix
are you using? If possible, we'd like to see the output from candle /? and
also the full text of your wxs file as an attached file to verify there aren't
other
Please be sure to run MSI validation on your msi files
before shipping them to customers. I think you'll find that using the same
short files will generate lots and lots of errors. You'll likely also
discover many other issues. light in WiX 3.0 automatically runs
validation, but in 2.0
could make a heat
plugin for harvesting a VS solution and create an install that could work
with Speech Server.
Now the question I have is, How do you create heat plugin (harvester?)
Thanks for your help!
Brandon
-Original Message-
From: Derek Cicerone [mailto:[EMAIL PROTECTED]
Sent
There are two issues:
1. We need to catch that DirectoryNotFoundException so that you don't get a
stack trace like that (please open a bug against it with the stack trace
from below in the description).
2. I just identified an issue with the WixUIExtension yesterday. There
really isn't a good
guess we'll stick where we are then. I could try and find a
version with the XML fix but not the IIS bug but I'm more likely to just write a
_vbscript_ CA to write out the value and tell people "it sucks but that's life".
Thanks
John
On 6/9/06, Derek
Cicerone [EMAIL PROTECT
Title: Message
We have a help extension that's been under development
internally - the plan is to incorporate this into the VS extension and release
it. You'll still need the help merge modules, but it should make this a
lot easier to deploy.
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Its probably good to note that msizap should be used sparingly because it's
a bit dangerous - it sometimes goes overboard in what it removes - so you
really want to make sure this tool is only used on development machines.
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone
Sent: Tuesday, June 13, 2006 11:37
AM
To: 'Christopher Painter';
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Dark Bug?
The package code of an MSM file is not the
same thing as the Module/@Guid.
PackageCode
-wix2/wix_xsd_simple_type_autogenuuid.htm
Derek Cicerone
[EMAIL PROTECTED] wrote:
Upon further investigation into this
issue, you appear to be correct about the correlation of the Revision Number
summary info property and the modularization guid. This means that the
way WiX currently
it work. MSI2XML and MSIDB worked just fine without
any effort and I wanted to let Simon know what to expect.
Derek Cicerone [EMAIL PROTECTED] wrote:
Christopher,
I'm sorry, but I think its a particularly unfair comment to say
that a bug in dark was scoffed to the side. I believe
Merge Module'
Manufacturer='My Company' InstallerVersion='100'
Compressed='yes'
SummaryCodepage='1252'
/
Thanks for your help. It's much
appreciated! -Jon
From: Derek Cicerone
[mailto:[EMAIL PROTECTED]
Sent: Monday, June 12, 2006 3:06
PM
To: 'Watkins, Jon';
wix-users
Right now, Rob is fixing the warnings that
make ClickThrough really painful to use. These were a result of recent
schema changes. Its some pretty exciting changes because
ClickThrough will utilize the same infrastructure as Heat. I expect the
innovation in this area to flourish once all
, 2006 10:30
AM
To: [EMAIL PROTECTED];
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Another
Sequencing issue
Next early next month.
From: Derek Cicerone [mailto:[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 12:38
PM
To: Scott Sam;
wix-users@lists.sourceforge.net
Subject
: [WiX-users] Another
Sequencing issue
I didnt see it anywhere in the
wixca.wxs file. What sources files do I need to edit?
From: Derek Cicerone [mailto:[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 1:38
PM
To: Scott Sam;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users
Title: Msi localization
You need to set Product/@Codepage
do not set SummaryCodepage at all its unnecessary since it defaults to
1252.
Derek
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of KERROUMI Rachid
Sent: Monday, June 19, 2006 2:02
AM
To:
The Id used in Merge and MergeRef is completely
arbitrary. Its used by wix to match up the Merge and MergeRef
elements. It can be whatever you want it to be.
The Id used in the Module element, however, must be a legal
identifier since its used to populate the ModuleSignature table.
Is it a terminal server session?
From: Don Tasanasanta [mailto:[EMAIL PROTECTED]
Sent: Monday, June 19, 2006 4:54
PM
To: Bob
Arnson
Cc: [EMAIL PROTECTED];
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] What
makes ClickThrough per-user?
i tried it on win2000 and
The latest version is 2.0.4208.0
so yours is about 9 months old its very likely the bug was fixed
in that time. Please try the latest release and let us know how it goes.
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brower, Jason
Sent: Monday, June
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone
Sent: Saturday, 17 June 2006 2:38
AM
To: 'Scott Sam';
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Another
Sequencing issue
In 2.0 youll need to manually
change the wixlibs to change the sequencing. Its very inconvenient
I agree - separate mailing list :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of david adams
Sent: Tuesday, June 20, 2006 4:48 PM
To: WiX-users@lists.sourceforge.net
Subject: Re: [WiX-users] job postings...
That was so simple that I was going to
In order to make the WiX schema more uniform in its handling
of advertised versus non-advertised COM registration and also dissuade people
from using the built-in MSI TypeLib functionality (which has some issues with
rollback and uninstall), weve changed the default for the TypeLib
Ive just posted a new blog entry at http://installing.blogspot.com/2006/06/ngen-support-in-wix.html
about the new support for NGen in WiX J
Derek
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
already have a couple of interesting blog posts up and
it would nice to have them in a central place!
Frederik
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone
Sent: woensdag 21 juni 2006 18:20
To:
WiX-users@lists.sourceforge.net
Subject: [WiX-users] NGen
Correct, the dll files are relative to the wixlib in 2.0. In WiX 3.0, there
is a single binary for extensions so this problem no longer occurs. It's a
pain in 2.0 :)
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of jdrake
Sent: Friday, June 23,
You need to place WixDifxAppExtension.dll
and the difx wixlib file (I dont know its name) in the same directory
with candle, lit, light, etc Then when calling candle, you need to
provide ext WixDifxAppExtension on the command line. Im not
sure if this is possible from within Votive at this
This is a common authoring mistake which is caught by MSI validation - be
sure to run validation on all your MSI files.
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, June 26, 2006 12:30 PM
To:
You're very close. Try this:
Candle -ext WixUtilExtension
Lit -ext WixUtilExtension
Light -ext WixUtilExtension
That's it - you don't even need to specify a wixlib file for light anymore -
it's all handled automatically. Additionally, if you automatically upgraded
your wxs source files using
This type of question normally indicates something fishy - why would you
want to unzip a zip file when you can associate cabinet files with an msi
rather easily? It's much better to keep files under MSI control because
then they will be patchable - otherwise you'll expose customers to a
security
NGen is supported in both WiX 2 and 3.
I would highly suggest using the custom actions we built since they were done
with assistance from the NGen team. There could be some bugs however, so
it probably isnt appropriate for shipping in a few days (a few months
would be much more appropriate
#
Regards,
Silvio
On 7/3/06, Derek Cicerone [EMAIL PROTECTED]
wrote:
The issue appears to be during the stream import. I
just made a fix in this code last week but it looks like it's not good
enough. If you can, you should debug into this issue and take a look
This is another simple rfc. Wed like to change
the COM registration written by the Class / element to be long file
names (versus the current short file names). In terms of how this will
affect MSI files, it basically means that instead of writing registry keys with
[!FileId], wed begin to
The validation data for the
MsiDriverPackages is likely wrong. Heres the current definition:
columnDefinition
name=Flags type=number length=4
set=0;1;2;3;4;5;6;7 description=Flags for installing and
uninstalling driver packages/
Clearly this is wrong since there can be a
flag of
could always check it's code...
Derek Cicerone wrote:
I'm not familiar with .ocx files - are they just like self-reg dll
files? If so, I can make a small modification to get that working
pretty quickly. If they are some other format of file, then we'd have
to write a special plugin to handle
I wonder if something like this could be covered by having the VSExtension
use the XmlFile stuff in the UtilExtension. Probably more complicated than
what you'd need, but if XmlFile became more like a platform, this could be
an easier way to go because then you can just focus on the xml changes
and LaunchConditions elements in every single
ca_*.wixlibfile because when the wrapper install is built, it sees
multiple of the same element and fails. We were hoping that the
Overridable attribute would allow for this functionality.
From: Derek
Cicerone [mailto:[EMAIL PROTECTED]
Sent: Monday
You didnt specify a culture for
light to use, so it didnt load any localization strings from the library.
Since wix libraries may contain multiple languages of localized strings, the
culture is necessary to pick one. In this case, youd probably want
en-us.
Derek
From: [EMAIL
the instructions above and it should work.
So this is either some problem where i'm
by mistake not including the wixlib or those elements in a wixlib that is
included in an install wrapper is not resulting in the tables and actions being
put in the msi.
From: Derek
Cicerone
What does the verbose installation log say? Have you verified that the msi
file is created with files?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Arto Stimms
Sent: Wednesday, July 12, 2006 2:00 PM
To: wix-users@lists.sourceforge.net
Subject:
Thats not a good idea
replying upon certain system registry values is an invitation for application
compatibility issues for future versions of the OS. Instead, just use the
built-in ComputerName property:
ComputerName
Property
The ComputerName property
is the computer name of the
Nested parenthesis is unsupported in both versions of WiX. Is that a
standard Windows environment variable or one which you are defining?
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey Altman
Sent: Tuesday, July 18, 2006 4:36 PM
To:
Files\Common Files
Jeffrey Altman
Derek Cicerone wrote:
Nested parenthesis is unsupported in both versions of WiX. Is that a
standard Windows environment variable or one which you are defining?
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Check out the ModuleInstallUISequence.
That table contains the UI actions for a merge module. One of the actions in
there was likely authored improperly and is colliding with an action in the
main msi.
Derek
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Youd have to do it via your own
custom action. What is your scenario? In general you should avoid
custom actions because its very difficult to write one
properly/securely.
Derek
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Eddie Tse
Sent: Thursday, July 20,
the
file in Binary table
Im trying to
deploy web services to an IIS site running Sharepoint along with some templates
that will be loaded as documents into the Sharepoint library.
Looks like just executing
an external command would be easier then.
Eddie
From: Derek Cicerone [mailto
Set the Impersonate attribute to yes
for that CustomAction element but then the CA doesnt run as
LocalSystem so it doesnt have elevated privileges.
Derek
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bahar Shah
Sent: Thursday, July 20, 2006
11:56 PM
To:
When will you be shipping to your customers? The current recommendation is
to only use 3.0 if your product ships in 2007 or later.
That being said, we've begun slowing down the pace of changes to the WiX 3.0
core tools for a few months now, but breaking changes are still being made
and I'd
.
Could you ellaborate a bit more.
Do you mean to say that just setting a impersonate attribute to 'yes' the
installer would know who the current logged user is and install under that
priveldge ?
Regards
Bahar
On 7/21/06, Derek
Cicerone [EMAIL PROTECTED]
wrote:
Set the Impersonate attribute
WiX 3.0 does not ship wixlib files because the WiX extensions are now
completely self-contained in each extension dll. You should see a
WixUIExtension.dll in the 3.0 releases. To use it, just specify -ext
WixUIExtension -cultures:en-us in light and you're done. This will pull in
the WiX UI
, and such.
Thanks,
John
Derek Cicerone [EMAIL PROTECTED] 7/22/2006 5:34 PM
WiX 3.0 does not ship wixlib files because the WiX extensions are now
completely self-contained in each extension dll. You should see a
WixUIExtension.dll in the 3.0 releases. To use it, just specify -ext
WixUIExtension
If you are migrating to WiX, please try using dark on your MSI files. The
WiX 3.0 dark.exe should be especially accurate for the conversion.
Beyond that, the authoring below nests a Shortcut under a component, which
creates a shortcut to the folder of the component. To create a shortcut to
a
Please update to the latest WiX 3.0 release. This error is due to
installing the WiX tools in a path with spaces and it has been fixed in the
latest releases.
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Klimek Manuel
Sent: Monday, July 24,
That means that the component needs to have a registry key under HKCU as its
keypath. This supports installation of per-user shortcuts for a per-machine
installation.
Alternatively, you could switch to advertised shortcuts by specifying
Advertise=yes on the Shortcut elements. However,
a reference to this issue. If you know
where the information is, please feel free to refer me to the proper
pages.
Thanks,
John
Derek Cicerone [EMAIL PROTECTED] 7/24/2006 3:21 PM
That means that the component needs to have a registry key under HKCU
as its
keypath. This supports installation
key in the User hive with a shortcut, perhaps I
could glean the syntax on my own. :)
Thanks in advance,
John
Derek Cicerone [EMAIL PROTECTED] 7/24/2006 4:32 PM
It's a very good question actually and I've seen no solid
recommendation on
a best-practice approach. I think you can create any HKCU
: Re: [WiX-users] ORCA validation issue with wix generated installer
Derek Cicerone wrote:
That means that the component needs to have a registry key under HKCU as
its
keypath. This supports installation of per-user shortcuts for a
per-machine
installation.
I don't see why anyone would ever want
Cheers,
Manuel
-Ursprüngliche Nachricht-
Von: Derek Cicerone [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 24. Juli 2006 18:23
An: Klimek Manuel; wix-users@lists.sourceforge.net
Betreff: RE: [WiX-users] -dWixUILicenseRtf method
Please update to the latest WiX 3.0 release. This error
.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone
Sent: Friday, July 21, 2006 12:35
PM
To: 'Bahar
Shah'; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users]
Installing a binary in context of current logged inuser
Set the Impersonate attribute to
yes
for
installingWindowsinstrumentation features?
From: Derek Cicerone [mailto:[EMAIL PROTECTED]
This is a good chance for us to all get on the same page. Who on the
PowerShell team is saying to use the Installer classes? (Or
if this is from
some MSDN docs, please send us the link.)
Here's
WiX 3.0 currently has the ability to read library (.wixlib)
files generated by the WiX 2.0 version of the toolset. However,
weve recently identified several reasons why wed like to stop
maintaining backwards-compatibility with the 2.0 format. The overall goal
here is to make the changes
WiX 3.0 has a very different method of customizing the dialogs than WiX 2.0
which is so far undocumented. It's (hopefully) much more simple.
Basically, just grab a sequence file from the sources that is similar to
what you want (like WixUI_Mondo.wxs) and put that in your sources and modify
it to
What are you trying to do overall?
Using feature conditions in a components condition is a little awkward
usually features directly determine if a component will be installed.
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Wednesday,
WiX 3.0 currently has the ability to read library (.wixlib)
files generated by the WiX 2.0 version of the toolset. However,
weve recently identified several reasons why wed like to stop
maintaining backwards-compatibility with the 2.0 format. The overall goal
here is to make the changes
this far
if you made it and thanks for the advice. Hope to keep the discussion
going.
Rick
From: Derek Cicerone [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 27, 2006
11:52 PM
To: Rick Glos;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Question:
Migrating Existing Installer
-users]
conditions
I need to write out to a config file what
features are being installed, so that the program that update/creates the
database knows what database to create/update if any at all.
From: Derek Cicerone
[mailto:[EMAIL PROTECTED]
Sent: Thursday, July 27, 2006 6:12
PM
The very latest WiX 3.0 release fixes this, enjoy! :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andrey T
Sent: Friday, July 28, 2006 4:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Long path name to COM server
Hello, all!
I have
This question has been coming up
often. Note that ALLUSERS is completely uppercase so a user can
change your installation to be per-user via the command line or several other
methods. This means that you need the HKCU key to ensure proper repair
operation (since a shortcut is not a valid
704.554.6300 support
704.943.0585 fax
[EMAIL PROTECTED]
www.clearskysoftware.com
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone
Sent: Wednesday, July 26, 2006
6:50 PM
To:
wix-users@lists.sourceforge.net
Subject: [WiX-users] rfc: break
WiX 3.0 backwards
Title: SelfRegCost on windows 2003 Server
Its probably a missing
dependency. It might be easier to stop using self reg by running tallow
(wix v2) or heat (v3) against the self-reg dll to collect its registry keys. J
Derek
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On
To resolve the localization issue: I think
youll need to pass cultures:en-us to light to load the English
resources for the extension. This change was just made in the last
release.
Please note that the custom action code in
WiX 3.0 is identical to what can be found in 2.0. We still
Weve recently discovered that the way WiX creates
merge modules is a little bit incorrect. Every merge module has a unique
guid which is used to modularize all the entries in the merge module (WiX does
this properly). However, that guid is also supposed to be used as the
package code
that is very difficult to
track.
I appreciate the
consistency proposed but I'm concerned about the potential for accidents.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone
Sent: Sunday, July 30, 2006 23:16
To: wix-users@lists.sourceforge.net
Subject: [WiX
, July 31, 2006 12:54 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to set one File for two Components
You could use CopyFile and RemoveFile elements, but it's much easier to just
include the file twice.
I'd only really consider this option if the file was huge.
Rob
Derek
You can probably just pretty print the
wixlib files and inspect them directly its just xml (unless you use the bf option
to bind files into it in which case its a cabinet file with xml appended to
the end).
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
I've been thinking about adding a warning to the LaunchConditions parsing
code in the compiler. In almost every case, you should add Installed OR
to the beginning to ensure it only runs during initial install.
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
What does the exe do to the xml file? WiX
has custom actions which support modifying xml files during setup. They
support rollback and install nothing to the target machine.
Derek
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Shmarya Rubenstein
Sent: Tuesday,
:39
PM
To: [EMAIL PROTECTED]
Cc:
wix-users@lists.sourceforge.net; [EMAIL PROTECTED]
Subject: Re: [WiX-users] rfc:
Package element changes
Derek Cicerone wrote:
That is an excellent point what if
we keep the ???... syntax just for Product/@Id in that case and go with the
recommendations
From: Derek Cicerone
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 01, 2006
3:09 PM
To: Don Tasanasanta;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] custom
action to write a reg value
Just write the registry key as part of the
normal installation why would that require
Tasanasanta
VIACK Corporation
425-605-7423
From: Derek Cicerone
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 01, 2006
3:29 PM
To: Don Tasanasanta;
[EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] custom
action to write a reg value
Why? Windows Installer
That's correct - we generate the entire guid every time.
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of DEÁK JAHN,
Gábor
Sent: Wednesday, August 02, 2006 1:14 AM
To: WiX-users
Subject: [WiX-users] rfc: Package element changes
On Tue, 1 Aug 2006
and may result
in undesirable behavior in some scenarios as well.
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone
Sent: Wednesday, August 02, 2006 1:24 AM
To: 'DEÁK JAHN, Gábor'; 'WiX-users'
Subject: Re: [WiX-users] rfc: Package element
Arnson
Sent: Wednesday, August 02, 2006 8:44 AM
To: [EMAIL PROTECTED]
Cc: 'DEÁK JAHN Gábor'; 'Rob Mensching'; 'WiX-users'
Subject: Re: [WiX-users] rfc: Package element changes
Derek Cicerone wrote:
I've done some more thinking about this. I think Rob's main objection
with
making Product/@Id
Be wary of level 0 for features - you can get into scenarios where it's
difficult to bring the features back to life :)
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Beaudet
Sent: Wednesday, August 02, 2006 2:01 PM
To:
You should not be referencing a custom action from a merge
module in a main installation. Who wrote the custom action? If its
yours then you should use wixlib files instead of merge modules. If its
not yours, whoever did write it should have made it a table-driven custom action.
Derek
Title: Performance issues
What are the install times like if you
disable system restore? Apparently MSI installations take a large
up-front hit while loading on system restore and disabling it (assuming you dont
use it), can speed things up quite a bit.
Derek
From:
[EMAIL
Im surprised Bob hasnt
responded to this yet J
Im not sure how it works in WiX
2.0, but in 3.0, doing something like this should be very easy since we moved
all the dialog flow into one file apiece for each of the dialog packs (mondo, minimal,
etc). You can just take the single file for
, August 03, 2006
3:52 PM
To: WiX-users
Subject: Re: [WiX-users] rfc:
Package element changes
From: Bob Arnson
Sent: Wed 8/2/2006 8:44 AM
Derek Cicerone wrote:
I've done some more thinking about this. I think Rob's main
objection with
making Product/@Id optional was that someone might
.)
***
When I took the steps, it appears that I am missing the pcaext.dll for the
reference and the pubca.wixlib. Are these not available in the bin
directory like wixca, etc.?
David Adams
MSN MessengerID: [EMAIL PROTECTED]
From: Derek Cicerone [EMAIL
Title: Multi-language msi
What is the MsiTran SummaryInfo mechanism?
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Lemire
Sent: Saturday, August 05, 2006
5:22 PM
To:
wix-users@lists.sourceforge.net
Subject: [WiX-users]
Multi-language msi
Hi,
We are
the current os/user setting with the
options in the SummaryInfo and if it matches one it applies that ones transfom
before showing the UI.
-Original Message-
From: Derek Cicerone [mailto:[EMAIL PROTECTED]]
Sent: Sat 8/5/2006 5:38 PM
To: John Lemire; wix-users@lists.sourceforge.net
Subject
:[EMAIL PROTECTED] On Behalf Of DEÁK JAHN,
Gábor
Sent: Sunday, August 06, 2006 1:28 PM
To: WiX-users
Subject: [WiX-users] Multi-language msi
On Sun, 6 Aug 2006 11:32:20 -0700, Derek Cicerone wrote:
Derek,
Its not officially supported by the MSI team (they
discourage people from using it). Im
Please give us an example of the authoring you are currently
trying.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Vijay
Kalasani
Sent: Monday, August 07, 2006 3:24 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Setting Page Count property...
Hi,
Page Count property...
In the property table using ORCA, I am trying to do the following
and the validation fails. Now I am looking at some documentation that suggests
setting properties using custom action (type 51).
Page Count 200
Thanks,
Vijay
From: Derek Cicerone
[mailto
in the Orca database) should I set it.
Thanks,
Vijay
From: Derek Cicerone
[mailto:[EMAIL PROTECTED]
Sent: Monday, August 07, 2006 3:47 PM
To: 'Vijay Kalasani'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Setting Page Count property...
Why are you using Orca? Everything
Thanks for the heads-up but that's not a crash - it's actually an ICE
warning (you can tell because it says ICE03 in front). When WiX crashes,
it will display a stack trace so that we can diagnose and fix the problem.
The problem you've encountered is that MSI identifiers are supposed to be 72
reading location 0x.
I got it to generate a minidump and I have attached it.
Does the fact I use .Net 1.1 and not 2.0 make a difference?
N
On 08/08/06, Derek Cicerone [EMAIL PROTECTED] wrote:
Thanks for the heads-up but that's not a crash - it's actually an
ICE warning (you can tell
It can't be controlled. Why does the order matter in your scenario?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peter G.
Sakhno
Sent: Tuesday, August 08, 2006 4:37 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] What is the order of
What will your custom action do?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Magus
Sent: Tuesday, August 08, 2006 10:48 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Using Multiple binary's
I have a .exe files that relies on a .dll
,
Peter G. Sakhno
C-MAP RUSSIA Ltd
http://www.c-map.ru/
Derek Cicerone wrote:
It can't be controlled. Why does the order matter in your scenario?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peter G.
Sakhno
Sent: Tuesday, August 08, 2006 4:37 AM
Starting with the latest release, we have now exposed all strings which
appear during installation in the extensions to localization. This means
that you now need to specify the language of strings you would like to use
when you run light. This can be done by providing -cultures:en-us on the
1 - 100 of 135 matches
Mail list logo
