What version of wix are you using? In 3.0, XmlFile belongs to an extension
(and thus a completely different namespace) so its technically not a legal
child of the Component element unless it has the proper namespace prefix.
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
You need to pass in "-ext WixUtilExtension" for the candle and light command
lines to use the util extension.
Authoring should look like this:
http://schemas.microsoft.com/wix/2003/01/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
...
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 inconvenie
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
othe
I thought it might be useful to add a quick comment about why dark is being
treated special and fixes aren't being ported back to 2.0. There are
several reasons: dark 3.0 is a complete re-write, so we can't directly port
changes back, and the 2.0 code was never fully utilized before we began to
lo
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 yo
Heat is still the baby of the WiX toolset so its got plenty of missing
features (like proper usage support).
The help syntax you used below isn't implemented yet (sorry). I meant to
add that in but I became very busy right after I introduced heat and haven't
been able to get back to it.
Regardin
.obj or .cs files.
Just thoughts.
Thanks!
Brandon
-Original Message-
From: Derek Cicerone [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 06, 2006 1:50 PM
To: Brandon Tyler; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] heat help with harvester arguments -
filteringdirectories and
ike I 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
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 work
D]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone
Sent: Wednesday, June 07, 2006 1:15 PM
To: Brandon Tyler; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WixUIExtension and DirectoryNotFoundException
There are two issues:
1. We need to catch that DirectoryNotFoundException so
mas.microsoft.com/wix/2003/01/wi'} if
matches.length > 1 count = 0 matches.each do
|m| short_file_name =
f.attributes['Name'].split('.')[0].slice(0..5) short_file_ext
= f.attributes ['Name'].split('.')[1].slice(0..2)
count = count +
1 m
time, the path shown is
from your machine. -James
On 5/23/06, Derek
Cicerone <[EMAIL PROTECTED]>
wrote:
Unfortunately,
I was referring to using a debugger. I know it's a pain soI'll
understand if you aren't interested in doing that. Seems likely
thatsomeone wil
We had to make some features 3.0-only otherwise no one
would ever adopt it :)
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brandon
TylerSent: Wednesday, June 07, 2006 1:52 PMTo:
wix-users@lists.sourceforge.netSubject: Re: [WiX-users] Unique Short
Names?
I had a funny bu
There are two separate issues here:
1. The warning about collisions is just that - a warning. If it doesn't
worry you, then you can simply suppress it with -sw1055 on the light
commandline. The warning is intended to alert you that two different merge
modules are colliding (which should never ha
the time being we're with WiX 2.0. I'm hearing good things about
3.0 though - like the fact that tallow will generate fragments that can be
plugged straight into a WiX project without too much work.
Thanks
On 6/8/06, Derek
Cicerone <[EMAIL PROTECTED]>
wrote:
Bette
If the limitation is the length of the string in the
column, we should fix that. However, I think these limits were adjusted
upwards a while ago. What version of wix are you using (as reported by
candle /?)?
Thanks,
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of J
;s
complaining because that happens to be quite long.
On 6/8/06, Derek
Cicerone <[EMAIL PROTECTED]>
wrote:
If the
limitation is the length of the string in the column, we should fix
that. However, I think these limits were adjusted upwards a while
ago. Wh
to give us fragments that we can just include. I'll have to look at
stripping all that stuff out of the build scripts.
Thanks
John
On 6/8/06, Derek
Cicerone <[EMAIL PROTECTED]>
wrote:
That build
is a few months stale and likely has the issue. You should just try
version of
2.0 which has the XML fix but not the IIS bug? It probably wouldn't be massively
hard to take out the references to Tallow.
Thanks
John
On 6/8/06, Derek
Cicerone <[EMAIL PROTECTED]>
wrote:
You should
just stick with 2.0 (but update to the latest release).
mean that 3.0 has the IIS bug as well?
Thanks
On 6/8/06, Derek
Cicerone <[EMAIL PROTECTED]>
wrote:
WiX 3.0
will have the same IIS problems as 2.0 - the code is identical for all the
extensions shared between 2 and 3. I'm not sure what version of wix (if
any)
..
Ok, I 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
What version of WiX are you using?
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of jhewes
Sent: Friday, June 09, 2006 4:50 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Localization of ScrollableText filename not working.
Hi, I'm new
f days ago.
-Original Message-----
From: Derek Cicerone [mailto:[EMAIL PROTECTED]
Sent: Friday, June 09, 2006 4:59 PM
To: 'jhewes'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Localization of ScrollableText filename not
working.
What version of WiX are you using?
Derek
-
ourceFile' attribute.
Jim
-Original Message-
From: Derek Cicerone [mailto:[EMAIL PROTECTED]
Sent: Friday, June 09, 2006 5:19 PM
To: 'jhewes'; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Localization of ScrollableText filename not
working.
I don't think the
ut $(loc.LicenseFilename) as the text in the title bar of the license
agreement dialog and that works; that is, it puts the actual filename in the
title bar. It just doesn't seem to work in the 'SourceFile' attribute.
Jim
-Original Message-
From: Derek Cicerone [mailto:[
What codepage are you setting for the package? Please
show the exact authoring being used because there are two codepages in an msi
package - one for the summary information and one for the package itself.
We need to ensure the proper one is being set.
Derek
From: [EMAIL PROTECTED]
[ma
I'm curious - is there any particular reason to have a
special property other than TARGETDIR for the install
location?
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob
ArnsonSent: Monday, June 12, 2006 2:37 PMTo: Neil
SleightholmCc: wix-users@lists.sourceforge.ne
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
That's a good one-off solution, but it would be cool if we could create a
solution in the extension itself so that everyone can leverage it without
additional work.
Putting the license text in the wxl file won't be good enough in WiX 2.0
because there is no ability to override that text. So you'd
Tweaking feature states via a custom action is a little heavy and pretty
dangerous in terms of getting all the behavior exactly right. If you have
two components that can never be installed at the same time, you could also
consider giving them conditions such that they never get installed
simultan
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 the
particular issue you are referring to dealt with dark creating output that when
compiled immediately produced errors. I would like to explain why that
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 P
Is it possible to create an uncompressed install image by
running an admin install? (I'm honestly not sure how well it would work -
just an idea)
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Simon
TopleySent: Tuesday, June 13, 2006 8:29 AMTo: 'Christopher
Painte
The package code of an MSM file is not the same thing as
the Module/@Guid.
PackageCode
The decompiler never persists a PackageCode because its
supposed to be unique for every single MSM/MSI/PCP file. Even if
you link the same MSI twice in a row, the guid is supposed to change. That
is wh
:[EMAIL PROTECTED] On Behalf Of Frederik
Carlier
Sent: Tuesday, June 13, 2006 10:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix Versions
[This message is BCC'd to wix-devs for those who are not subscribed to
wix-users, but I think it is worth keeping the discussion on wix-users on
From: [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 Mo
://wix.sourceforge.net/manual-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 t
Probably due to your delayed mail –
we’ve already got a bug opened against him J
From: Rob Mensching
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 13, 2006 7:08
PM
To: 'Christopher Painter';
[EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Dark Bug?
Definitely a bug in tallow. Tallow
has basically been deprecated in favor of heat (which works with WiX 3.0). You
can open a bug against tallow, but depending upon the size of the fix, it may
not happen. I know this is a little difficult for the time being, but the
hope is to start migrat
mailto:[EMAIL PROTECTED] Namens Frederik Carlier
Verzonden: dinsdag 13 juni 2006 19:47
Aan: wix-users@lists.sourceforge.net
Onderwerp: [WiX-users] Wix Versions
[This message is BCC'd to wix-devs for those who are not subscribed to
wix-users, but I think it is worth keeping the discussion on
If I export and
import using MSI2XML its fine. If I merge the modules into an
installer it's fine.
I've really tried to open the door and fit WiX into my existing installer
solution but I just got tired of banging my head against the wall trying to
make it work. MSI2XML and MSIDB worke
Search
patterns. Dark fails to extract the PID_REVNUMBER out of the Summary
Information stream on nearly 40% of them. When I try to candle them
they fail since they don't have a valid identifier. If I look at
the summary info in Orca they are fine. If I export and import using
MSI2XML its f
rainingAppModule' Guid='6E51C103-AF1B-4952-B5AD-958BD96B9EA3' Language='1033' Version='3.0.0.0' Codepage='1252'>
<Package Id='----' Description='Training
App Merge Module'
Commen
Right now, Rob is fixing the warnings that
make ClickThrough really painful to use. These were a result of recent
schema changes. It’s some pretty exciting changes because
ClickThrough will utilize the same infrastructure as Heat. I expect the
innovation in this area to flourish once all
There’s actually quite a bit that
can be done in designing how a wix setup is organized and integrated with a
build process. It becomes particularly interesting for groups which ship 40
languages times a hundred or so SKUs (you can guess who these groups might be)
because the amount of aut
DifxApp functionality was removed from the native wix schema and put into an
extension - WixDifxAppExtension. To fix your authoring, you can do the
following:
1. Run "wixcop -f *.wxs" to fix your sources files for the new schema (this
will also modify whitespace so be sure to backup your sources b
Are you using WiX 2.0 or 3.0? I’m
pretty sure this should work in 3.0 but probably not 2.0.
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Friday, June 16, 2006 8:41
AM
To:
wix-users@lists.sourceforge.net
Subject: [WiX-users] Another
Se
];
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Another
Sequencing issue
2.0
From: Derek Cicerone [mailto:[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 11:49
AM
To: Scott Sam;
wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Another
Sequencing issue
Are
, June 16, 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: RE: [WiX-users] Another
Sequencing issue
I didn’t 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
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:
wix-users@l
The Id used in Merge and MergeRef is completely
arbitrary. It’s 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 it’s 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 your’s 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, J
:
[EMAIL 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 you’ll need to manually
change the wixlibs to change the sequencing.
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 suggest
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), we’ve changed the default for the TypeLib
element
I’ve 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
https://lists.sourceforge.net/l
? You 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
The error is E_ADS_BAD_PATHNAME: An
invalid directory pathname was passed
Seems likely that the website path
provided on the commandline was invalid.
Derek
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jon Hardenbrook
Sent: Friday, June 23, 2006 5:14
AM
Did you specify the necessary -ext option on the command line for candle to
use the extension?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of jdrake
Sent: Friday, June 23, 2006 10:46 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] COM+ cus
Title: Re: [WiX-users] FW: COM+ custom actions
It’s supposed to be case-insensitive
because you are specifying a class name directly. In WiX 3.0 you can merely
specify the assembly name of the extension (which is case-insensitive). Please
do not open a bug on this issue since its by-desig
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, 200
What is the root of all these directories? Do they all get created under a
machine location like "Program Files" or a per-user location like the user
profile?
Thanks,
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Voranc Kutnik
Sent: Monday, June
You need to place WixDifxAppExtension.dll
and the difx wixlib file (I don’t 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. I’m not
sure if this is possible from within Votive at
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: wix-users@lists.source
)
.,.,..,...,.,,.
Justin E. Pitts, Lead Technical Analyst
Data and Application Integration Services
BIG LOTS -- World's Best Bargain Place
"Derek Cicerone"
Title: Getting current shared application data folder
It’s not necessary to call that API –
Windows Installer already does it for you behind the scenes. Check out http://msdn.microsoft.com/library/default.asp?url="">
Derek
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] O
#x27;s Best Bargain Place
"Derek Cicerone"
<[EMAIL PROTECTED]
rceforge.net> To
Title: Wix3.0: Heat.exe - harvesting web site
That’s close. I think you can
use something like:
heat website “Default Web Site”
–out test.wxs
Be sure to use –out (not –o),
and specify the website name in the proper case.
Derek
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PRO
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 Wix
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 t
to avoid the complexity of having to deal with hundreds of
different version numbers and GUIDs. I'm concerned that some
mistake may make it fail to upgrade.
*** End of long-winded background
I've read through the wix tutorial. I'm trying to reduce the
great complexity I'
Can you run light with verbose logging on
so we can get an idea of where the issue occurred?
Thanks,
Derek
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Silvio Massari
Sent: Monday, July 03, 2006 7:45
AM
To:
wix-users@lists.sourceforge.net
Subject: [WiX-use
ICE33 is very contentious – please note
that WiX suppresses this ICE by default when running validation in WiX
3.0. The WiX team suggests using the Registry table for all COM
registration to avoid unwanted advertised COM repair and demand installation
behavior. You won’t see too many exam
le is at c:\wix folder too.
Thanks for your time.
Silvio
On 7/3/06, Derek Cicerone <[EMAIL PROTECTED]>
wrote:
Can you run light with verbose logging on so we can get an
idea of where the issue occurred?
Thanks,
Derek
From: [EMAIL PROTECTED]
[mailto:[EMAIL
The Installer object in wix.dll is not
intended as a public interface – it will be changed to an internal class
shortly – please do not use it.
Thanks,
Derek
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Jiamin Zhu
Sent: Monday, July 03, 2006 12:10
PM
To:
[
missing file?
Thanks
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
actually possible to open/compile
the project with VS Express?
Thanks and regards,
Thomas
Von:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Derek Cicerone
Gesendet: Montag, 3. Juli 2006
22:06
An: 'Silvio Massari';
wix-users@lists.sourceforge.net
Betreff: Re:
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 isn’t appropriate for shipping in a few days (a few months
would be much more appropria
imensions:[1]}) Line 496 + 0x1d bytes C#
light.exe!Microsoft.Tools.WindowsInstallerXml.Tools.Light.Main(string[] args =
{Dimensions:[1]}) Line 108 + 0xc bytes C#
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 c
This is a pretty simple rfc. We’d like to make
it easier to distinguish between WiX 2.0 and 3.0 xml by giving 3.0 xml a unique
schema namespace.
The current WiX schema namespace is:
http://schemas.microsoft.com/wix/2003/01/wi
The WiX 3.0-only namespace could be:
http://schemas.mi
This is another simple rfc. We’d like to change
the COM registration written by the 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], we’d begin to use
.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone
Sent: Thursday, July 06, 2006
11:57 AM
To:
wix-users@lists.sourceforge.net
Subject: [WiX-users] rfc: change
wix 3.0 schema namespace
This is a pretty simple rfc. We’d like to make
it easier to distinguish
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 it – which would be a much longer
task.
Derek
All components need to belong to a feature
(for products) or Module (for merge modules). Put the appropriate
under your Module element to fix the error.
Derek
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Shmarya Rubenstein
Sent: Sunday, July 09, 2006 7:44
The validation data for the
MsiDriverPackages is likely wrong. Here’s the current definition:
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 0x10 (16). Please ope
les, so we 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
x for this...
By the way, where is this validation data found? In the XSD for the difx
extension?
Thanks,
Shmarya
Derek Cicerone wrote:
>
> The validation data for the MsiDriverPackages is likely wrong. Here's
> the current definition:
>
>
> set="0;1;2;3;4
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 yo
Localization strings are not evaluated during compilation. Something else
is going on here. Laurent, could you please tell us what version of wix you
are using?
Thanks,
Derek
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Simoneau
Sent: Monday, J
lt, 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, July 10, 2006 1:20
PM
To: Wilson, Brad;
wix-devs@lists.sourceforge.n
You didn’t specify a culture for
light to use, so it didn’t 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, you’d probably want
“en-us”.
Derek
From:
3.0.1821.0
I saw one other thing: "[ProductName]" is not replaced by it's value.
Thanks,
Laurent
Derek Cicerone a écrit :
> Localization strings are not evaluated during compilation. Something else
> is going on here. Laurent, could you please tell us what version of
ake 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 [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 2:28
PM
To: Wilson, Brad;
wix-devs@lists.so
;ve been a huge help.
From: Derek
Cicerone [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 7:00
PM
To: Wilson, Brad;
wix-devs@lists.sourceforge.net; wix-users@lists.sourceforge.net
Subject: RE: [WiX-devs] WiX
v3.0.1828.0 Overridable attribute causing buildbreak.
inline
We’ve already implemented this functionality
in WiX 3.0 and it’s used in the WiX standard UI library. Take a
look at WixUI_InstallDir.wxs, WixUI_Mondo.wxs, etc… in the WiX 3.0
sources to see how it works. Please note that you do not have to use
Property elements as we do in that code curr
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: [WiX-use
rge module is
not being installed without dummey file+shortcut (I
tried removing just the shortcut, but it didn't work),
or mayby ideas for a workaround?
Best Regards,
Arto Stimms
--- Derek Cicerone <[EMAIL PROTECTED]>
wrote:
> What does the verbose installation log say? Have
>
1 - 100 of 253 matches
Mail list logo
