Thanks,I'll patch it in my local copy so I can keep working...On 7/10/06, Derek Cicerone <[EMAIL PROTECTED]
> wrote:The MSI validation data for the Difx extension is inwix\src\ext\DifxAppExtension\wixext\Data\tables.xml. The schema for the
extension's xml is in the xsd file.Derek-Original Mess
Derek Cicerone wrote:
> 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 ju
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
The MSI validation data for the Difx extension is in
wix\src\ext\DifxAppExtension\wixext\Data\tables.xml. The schema for the
extension's xml is in the xsd file.
Derek
-Original Message-
From: Shmarya Rubenstein [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 09, 2006 12:37 PM
To: [EMAIL PR
If they work with regsvr32 they should be the same as normal self-reg dll
files (a simple fix). Please open a feature request (with an ocx file if
possible for testing purposes) and assign it to me; I'll get to it soon
since it's simple.
Thanks,
Derek
-Original Message-
From: Shmarya Rub
Has been an ongoing problem – I believe
Rob had some problems deleting/renaming the offending folder. I have just
switched off CVS and rely on the regular source .zip drops – doesn’t
help with submitting changes though.
Subbu
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Gordon Watts wrote:
> I've got a further question. Is it possible to extend the WiX schema
> to add a new install item. For example, I work a lot with installers
> that install libraries for VS. I'd love to have a simple install action
> that looked like Source="blah" />. This would invoke some
X Y wrote:
> 2. If it hasnt been, obtain dotnetfx from a website or
> somewhere and launch it.
>
That needs to be handled via a bootstrapper/chainer (such as the one in
WiX v3's ClickThrough project), because .NET is installed via an MSI and
you can't have two MSIs running at the same time.
-
Done. Request #1519658
(http://sourceforge.net/tracker/index.php?func=detail&aid=1519658&group_id=105970&atid=642714).
Please let me know when there is a fix for this...
By the way, where is this validation data found? In the XSD for the difx
extension?
Thanks,
Shmarya
Derek Cicerone wrote:
I believe they are the same as self-reg dlls. Both are registered using
regsvr32
Tallow knew how to handle these files, 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 modificat
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
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
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
Hi all,I updgraded my version of WiX + extensions to the latest HEAD (3.0), and all of a sudden this error crops up: error LGHT0204 : ICE03: Value not a member of the set; Table: MsiDriverPackages, Column: Flags, Key(s): Drivers__.B3C0C110_C664_4422_8204_4E6688F37C8A
My tag looks like this: The
Any ideas?On 7/4/06, Shmarya Rubenstein <[EMAIL PROTECTED]> wrote:
Ok, added that now I'm getting: warning LGHT1010 : Found orphaned Component 'ProgramsMenu'. Every Component should have at least one parent Feature. error
LGHT0204 : ICEM05: The component
ProgramsMen
Hi all,Heat is the successor to tallow in wix 3.0 right?How do I get it to generate registry entries for registration of COM components (specifically .ocx files). heat file myfile.ocx -out test.wxs
just gives me the element (in the correct components...)Help!?!Thanks,-- Shmarya
Hi,
Thanks! WixCop fixed almost all my errors (Other than the FragmentRef,
which I did by hand). Further, after adding the two missing .cub files
in the same directory as the executables installed with Votive
everything worked.
I've got a further question. Is it possible to extend the WiX sche
17 matches
Mail list logo