Re: [WiX-users] Problems with Heat and COM (and subsequently Candleand Light)

2009-05-19 Thread Ondrej Zarevucky
Thank you for your reply.
I was using RC2, but when I ran into problems I've downloaded the 
wix3-binaries.zip from http://wix.sourceforge.net/releases/3.0.5315.0/ and 
tried to use them. It didn't help :( But I still have RC2 installed in 
Program Files... I hope this is not a problem.

3) For the problem with 1252 codepage I forgot to include example:
The source WXS has (saved in utf-8): Prurez zadaný císelne
I've converted it to use only 1252 codepage characters (saved in utf-8): 
Prurez zadaný císelne, but it still throws the error:

Legacy.wxs(523) : error LGHT0311 : A string was provided which do
esn't match the specified database codepage '1252'. Either set your database 
cod
epage to match these characters, or change these characters to ones that 
exist i
n the database's codepage.

Ondrej Zarevucky

- Original Message - 
From: Neil Sleightholm n...@x2systems.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Tuesday, May 19, 2009 11:45 AM
Subject: Re: [WiX-users] Problems with Heat and COM (and subsequently 
Candleand Light)


 Could you confirm what version of WiX would are using, I think 2 may
 have been fixed in v3.0.5315.0.

 Neil

 -Original Message-
 From: Ondrej Zarevucky [mailto:ondrej.zarevu...@fine.cz]
 Sent: 19 May 2009 10:25
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] Problems with Heat and COM (and subsequently Candle
 and Light)

 Hi everybody,
 Thank the Wix developers for such great tool for making installations!
 I've
 been using Wix for a few weeks and I love it, but I'm having a few
 issues
 with the Heat tool generating wrong WXS files with COM objects. I'm
 sorry if
 it was reported before, but I couldn't find any search solution for this

 mailing list (the web interface
 http://sourceforge.net/mailarchive/forum.php?forum_name=wix-users
 doesn't
 seem to provida any)

 1) Heat is generating empty Description attributes for the COM objects,
 but
 this throws errors in Candle. Can you disable generating empty
 Description
 attributes? I've already written a tool, which removes them, but it
 seems
 this should be done by Heat itself.

 FRTopology.wxs(14) : error CNDL0006 : The Class/@Description attribute'
 s value cannot be an empty string.  If you want the value to be null or
 empty, s
 imply remove the entire attribute.

 Part of WXS source generated by Heat:
Component Id=FRTopology.dll
 Guid={ABF39CD0-EFCD-4DE1-871B-A541E957F9A3}
File Id=FRTopology.dll KeyPath=yes
 Source=SourceDir\FRTopology.dll
TypeLib Id={913A00C0-E8C0-4BC9-9429-90EA9C553766}

 Description=Fine Topology Library HelpDirectory=Solvers Language=0

 MajorVersion=1 MinorVersion=0
Class
 Id={6186A93C-1213-46B4-B3E5-EE1A6FC13647}
 Context=InprocServer32 Description= ThreadingModel=apartment
 Version=1.0
ProgId Id=FRTopology.Tp2DSorter
 Description= /
/Class
Class
 Id={92BCDFC0-8A81-4AC0-8248-991BD54A60D9}
 Context=InprocServer32 Description= ThreadingModel=apartment
 Version=1.0
ProgId Id=FRTopology.Tp2DCorrector
 Description= /
/Class
/TypeLib
/File
RegistryValue Root=HKCR Key=Interface Value=
 Type=string Action=write /
/Component


 2) I have one COM object, for which Heat and Candle works fine, but
 Light
 generates an error of duplicate registry key entry:

 FRFEMesh2d.wxi(14) : error LGHT0130 : The primary key 'reg7B7D6016
 89B9EB3643720FF03160A52E' is duplicated in table 'Registry'.  Please
 remove
 one
 of the entries or rename a part of the primary key to avoid the
 collision.

 The source WXS generated by Heat:
Component Id=FRFEMesh2D.dll
 Guid={5240A417-FBE3-4E10-9AD8-B3E0F59D7BEA}
File Id=FRFEMesh2D.dll KeyPath=yes
 Source=SourceDir\FRFEMesh2D.dll
Class Id={1CE686A7-CA82-4C61-820E-EDC6E846D6C8}
 Context=InprocServer32 Description=FEMeshGen2DGenerator Class
 ThreadingModel=both
ProgId Id=FRFEMesh2D.FEMeshGen2DGenerator
 Description=FEMeshGen2DGenerator Class /
ProgId Id=FRFEMesh2D.FEMeshGen2DGenerator.1
 Description=FEMeshGen2DGenerator Class /
/Class
Class Id={DED6C3C1-538B-477E-AEDB-D7B6BFFBA887}
 Context=InprocServer32 Description=FEMeshGen2DOptimizer Class
 ThreadingModel=both
ProgId Id=FRFEMesh2D.FEMeshGen2DOptimizer
 Description=FEMeshGen2DOptimizer Class /
ProgId Id=FRFEMesh2D.FEMeshGen2DOptimizer.1
 Description=FEMeshGen2DOptimizer Class /
/Class
TypeLib Id={DB9CDFE3-B353-4B5C-957E-C7B6644718AA}

 Description=FRFEMesh2D 1.0 Type Library HelpDirectory=Solvers
 Language=0 MajorVersion=1 MinorVersion=0 /
/File

Re: [WiX-users] Problems with Heat and COM (and subsequently Candleand Light)

2009-05-19 Thread Neil Sleightholm
I would suggest raising a bug for each of these with a sample file if you can.

Neil

-Original Message-
From: Ondrej Zarevucky [mailto:ondrej.zarevu...@fine.cz] 
Sent: 19 May 2009 12:01
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problems with Heat and COM (and subsequently Candleand 
Light)

Thank you for your reply.
I was using RC2, but when I ran into problems I've downloaded the 
wix3-binaries.zip from http://wix.sourceforge.net/releases/3.0.5315.0/ and 
tried to use them. It didn't help :( But I still have RC2 installed in 
Program Files... I hope this is not a problem.

3) For the problem with 1252 codepage I forgot to include example:
The source WXS has (saved in utf-8): Prurez zadaný císelne
I've converted it to use only 1252 codepage characters (saved in utf-8): 
Prurez zadaný císelne, but it still throws the error:

Legacy.wxs(523) : error LGHT0311 : A string was provided which do
esn't match the specified database codepage '1252'. Either set your database 
cod
epage to match these characters, or change these characters to ones that 
exist i
n the database's codepage.

Ondrej Zarevucky

- Original Message - 
From: Neil Sleightholm n...@x2systems.com
To: General discussion for Windows Installer XML toolset. 
wix-users@lists.sourceforge.net
Sent: Tuesday, May 19, 2009 11:45 AM
Subject: Re: [WiX-users] Problems with Heat and COM (and subsequently 
Candleand Light)


 Could you confirm what version of WiX would are using, I think 2 may
 have been fixed in v3.0.5315.0.

 Neil

 -Original Message-
 From: Ondrej Zarevucky [mailto:ondrej.zarevu...@fine.cz]
 Sent: 19 May 2009 10:25
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] Problems with Heat and COM (and subsequently Candle
 and Light)

 Hi everybody,
 Thank the Wix developers for such great tool for making installations!
 I've
 been using Wix for a few weeks and I love it, but I'm having a few
 issues
 with the Heat tool generating wrong WXS files with COM objects. I'm
 sorry if
 it was reported before, but I couldn't find any search solution for this

 mailing list (the web interface
 http://sourceforge.net/mailarchive/forum.php?forum_name=wix-users
 doesn't
 seem to provida any)

 1) Heat is generating empty Description attributes for the COM objects,
 but
 this throws errors in Candle. Can you disable generating empty
 Description
 attributes? I've already written a tool, which removes them, but it
 seems
 this should be done by Heat itself.

 FRTopology.wxs(14) : error CNDL0006 : The Class/@Description attribute'
 s value cannot be an empty string.  If you want the value to be null or
 empty, s
 imply remove the entire attribute.

 Part of WXS source generated by Heat:
Component Id=FRTopology.dll
 Guid={ABF39CD0-EFCD-4DE1-871B-A541E957F9A3}
File Id=FRTopology.dll KeyPath=yes
 Source=SourceDir\FRTopology.dll
TypeLib Id={913A00C0-E8C0-4BC9-9429-90EA9C553766}

 Description=Fine Topology Library HelpDirectory=Solvers Language=0

 MajorVersion=1 MinorVersion=0
Class
 Id={6186A93C-1213-46B4-B3E5-EE1A6FC13647}
 Context=InprocServer32 Description= ThreadingModel=apartment
 Version=1.0
ProgId Id=FRTopology.Tp2DSorter
 Description= /
/Class
Class
 Id={92BCDFC0-8A81-4AC0-8248-991BD54A60D9}
 Context=InprocServer32 Description= ThreadingModel=apartment
 Version=1.0
ProgId Id=FRTopology.Tp2DCorrector
 Description= /
/Class
/TypeLib
/File
RegistryValue Root=HKCR Key=Interface Value=
 Type=string Action=write /
/Component


 2) I have one COM object, for which Heat and Candle works fine, but
 Light
 generates an error of duplicate registry key entry:

 FRFEMesh2d.wxi(14) : error LGHT0130 : The primary key 'reg7B7D6016
 89B9EB3643720FF03160A52E' is duplicated in table 'Registry'.  Please
 remove
 one
 of the entries or rename a part of the primary key to avoid the
 collision.

 The source WXS generated by Heat:
Component Id=FRFEMesh2D.dll
 Guid={5240A417-FBE3-4E10-9AD8-B3E0F59D7BEA}
File Id=FRFEMesh2D.dll KeyPath=yes
 Source=SourceDir\FRFEMesh2D.dll
Class Id={1CE686A7-CA82-4C61-820E-EDC6E846D6C8}
 Context=InprocServer32 Description=FEMeshGen2DGenerator Class
 ThreadingModel=both
ProgId Id=FRFEMesh2D.FEMeshGen2DGenerator
 Description=FEMeshGen2DGenerator Class /
ProgId Id=FRFEMesh2D.FEMeshGen2DGenerator.1
 Description=FEMeshGen2DGenerator Class /
/Class
Class Id={DED6C3C1-538B-477E-AEDB-D7B6BFFBA887}
 Context=InprocServer32 Description=FEMeshGen2DOptimizer Class
 ThreadingModel=both
ProgId Id=FRFEMesh2D.FEMeshGen2DOptimizer
 Description=FEMeshGen2DOptimizer Class /
   

Re: [WiX-users] Problems with Heat and COM (and subsequently Candleand Light)

2009-05-19 Thread Simon Dahlbacka
On Tue, May 19, 2009 at 2:01 PM, Ondrej Zarevucky
ondrej.zarevu...@fine.czwrote:

 Thank you for your reply.
 I was using RC2, but when I ran into problems I've downloaded the
 wix3-binaries.zip from http://wix.sourceforge.net/releases/3.0.5315.0/ and
 tried to use them. It didn't help :( But I still have RC2 installed in
 Program Files... I hope this is not a problem.

 3) For the problem with 1252 codepage I forgot to include example:
 The source WXS has (saved in utf-8): Prurez zadaný císelne
 I've converted it to use only 1252 codepage characters (saved in utf-8):
 Prurez zadaný císelne, but it still throws the error:




 Legacy.wxs(523) : error LGHT0311 : A string was provided which do
 esn't match the specified database codepage '1252'. Either set your
 database
 cod
 epage to match these characters, or change these characters to ones that
 exist i
 n the database's codepage.


shouldn't the .wxs file itself be saved as 1252?
--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Problems with Heat and COM (and subsequently Candleand Light)

2009-05-19 Thread Bob Arnson
Ondrej Zarevucky wrote:
 I was using RC2, but when I ran into problems I've downloaded the 
 wix3-binaries.zip from http://wix.sourceforge.net/releases/3.0.5315.0/ and 
 tried to use them. It didn't help :( But I still have RC2 installed in 
 Program Files... I hope this is not a problem.
   

It might be, depending on how you're using it. Just install the 5315 
WiX3.msi -- it will upgrade your installation of RC2.

-- 
sig://boB
http://joyofsetup.com/



--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users