Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-05-13 Thread Roy Abou Assaly 
.
 
 If anything is unclear, let me know.  Thanks again,
 
 Roy
 
 
 Neil Sleightholm wrote:
 
 I am not sure I understand what you are asking, could you explain?
 
 Neil
 
 -Original Message-
 From: Roy Abou Assaly [mailto:royass...@gmail.com] 
 Sent: 24 April 2009 16:02
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
 
 
 Can anyone run light 3.0.5217 on this to confirm this?  The merge module
 simple won't build and that Interface element is indeed needed.
 
 Thanks again.
 
 
 Roy Abou Assaly wrote:
 
 Oh, and one more:
 
 00020420---C000-0046
 
 After that, I was able to build my merge module and link them and
 create
 my MSI which contains 129 vb6 com DLLs and various OCXs.  Again, my
 experience in this area is weak, but the product seems to install and
 uninstall without issues even though I remove those elements that I
 didn't
 fully understand.
 
 So I went and test the application, and of course, it threw an error
 saying the Interface isn't registered, which makes sense since I
 removed
 them.  So my ignorance has cost me.  I really need those interface
 elements or else the application won't work.
 
 
 Roy Abou Assaly wrote:
 
 Still kind of stuck.  I was able to generate the exact xml as Brian
 did. 
 Candle compiled fine, but light is complaining.  I'm trying to
 generate a
 merge module out of it.  Getting this error:
 
  [exec] D:\Builds\PRISM XP\Build
 11.51.\Bin\PrismShell.wxs(18) :
 error LGHT0130 : The primary key 'reg0387C011F3
 F8A22BDFC14B72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918' is
 duplicated in table 'Registry'.  Please remove one of the entries or
 rename a part of the primary key to avoid the collision.
 
 D:\Builds\PRISM XP\Build 11.51.\Bincandle -v PrismShell.wxs
 Microsoft (R) Windows Installer Xml Compiler version 3.0.5217.0
 Copyright (C) Microsoft Corporation. All rights reserved.
 
 PrismShell.wxs
 
 D:\Builds\PRISM XP\Build 11.51.\Binlight -v PrismShell.wixobj
 Microsoft (R) Windows Installer Xml Linker version 3.0.5217.0
 Copyright (C) Microsoft Corporation. All rights reserved.
 
 Updating file information.
 Creating cabinet files.
 Creating cabinet
 'C:\Users\roy\AppData\Local\Temp\jyewbz0r\#MergeModule.CABinet'.
 Generating database.
 D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(18) : error
 LGHT0130 : The primary key 'reg0387C011F3F8A22BDFC14B
 72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918' is duplicated in
 table
 'Registry'.  Please remove one of the entries or
  rename a part of the primary key to avoid the collision.
 
 My merge module looks like this:
 
 ?xml version=1.0 encoding=utf-8?
 Wix xmlns:wi=http://schemas.microsoft.com/wix/2006/wi;
 xmlns=http://schemas.microsoft.com/wix/2006/wi;
   Module Id=PrismShell Language=1033 Version=1.0.0.0
 Package Id=C7AC8538-65ED-4C2B-AE16-6291871D0918
 Description=PRISM
 Shell Module Comments=PRISM Shell Merge Module Manufacturer=Acme
 InstallerVersion=300
 /Package
 Icon Id=PRISM.ICO SourceFile=PRISM.exe
 /Icon
 Directory Id=TARGETDIR Name=SourceDir
   Directory Id=ProgramFilesFolder Name=Program Files
 Directory Id=HOCDir Name=Acme
   Directory Id=INSTALLLOCATION Name=PRISM Shell
   Component Id=DisplayFridayListUI.dll
 Guid={77B6CDD1-B9C6-4497-B7F5-242B9783D6A3}
   File Id=DisplayFridayListUI.dll
 KeyPath=yes
 Source=SourceDir\DisplayFridayListUI.dll
   TypeLib
 Id={3515D627-3FA0-490F-9330-02A73023E0C0}
 Description=DisplayFridayListUI HelpDirectory=TARGETDIR
 Language=0
 MajorVersion=1 MinorVersion=0
   Class
 Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
 Context=InprocServer32
 Description=DisplayFridayListUI.CDisplayFridayList
 ThreadingModel=apartment Version=1.0 Programmable=yes
   ProgId
 Id=DisplayFridayListUI.CDisplayFridayList
 Description=DisplayFridayListUI.CDisplayFridayList /
   /Class
   Interface
 Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
 Name=CDisplayFridayList
 ProxyStubClassId={00020424---C000-0046}
 ProxyStubClassId32={00020424---C000-0046} /
   /TypeLib
   /File
   RegistryValue Root=HKCR
 Key=CLSID\{9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}\Implemented
 Categories\{40FC6ED5-2438-11CF-A3DB-080036F12502} Value=
 Type=string
 Action=write /
   RegistryValue Root=HKCR
 Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid
 Value={00020424---C000-0046} Type=string
 Action=write /
   RegistryValue Root=HKCR

 Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid32
 Value={00020424---C000-0046} Type=string
 Action

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-05-13 Thread Brian Rogers 
 not linking with Light.
 
  This is where I am right now.  Please note that the XML that Heat
  produces in 3.0.4923 is much, much bigger than in 3.0.5217 and 3.0.5224.
  Let me know if you need me to send you a binary
 (DisplayFridayListUI.dll)
  that can reproduce this.
 
  If I can't resolve this issue, I'm afraid I will have to stick with
  3.0.4923 as 3.0.5224 has a break that I can't work around.
 
  If anything is unclear, let me know.  Thanks again,
 
  Roy
 
 
  Neil Sleightholm wrote:
 
  I am not sure I understand what you are asking, could you explain?
 
  Neil
 
  -Original Message-
  From: Roy Abou Assaly [mailto:royass...@gmail.com]
  Sent: 24 April 2009 16:02
  To: wix-users@lists.sourceforge.net
  Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
 
 
  Can anyone run light 3.0.5217 on this to confirm this?  The merge
 module
  simple won't build and that Interface element is indeed needed.
 
  Thanks again.
 
 
  Roy Abou Assaly wrote:
 
  Oh, and one more:
 
  00020420---C000-0046
 
  After that, I was able to build my merge module and link them and
  create
  my MSI which contains 129 vb6 com DLLs and various OCXs.  Again, my
  experience in this area is weak, but the product seems to install and
  uninstall without issues even though I remove those elements that I
  didn't
  fully understand.
 
  So I went and test the application, and of course, it threw an error
  saying the Interface isn't registered, which makes sense since I
  removed
  them.  So my ignorance has cost me.  I really need those interface
  elements or else the application won't work.
 
 
  Roy Abou Assaly wrote:
 
  Still kind of stuck.  I was able to generate the exact xml as Brian
  did.
  Candle compiled fine, but light is complaining.  I'm trying to
  generate a
  merge module out of it.  Getting this error:
 
   [exec] D:\Builds\PRISM XP\Build
  11.51.\Bin\PrismShell.wxs(18) :
  error LGHT0130 : The primary key 'reg0387C011F3
  F8A22BDFC14B72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918' is
  duplicated in table 'Registry'.  Please remove one of the entries or
  rename a part of the primary key to avoid the collision.
 
  D:\Builds\PRISM XP\Build 11.51.\Bincandle -v PrismShell.wxs
  Microsoft (R) Windows Installer Xml Compiler version 3.0.5217.0
  Copyright (C) Microsoft Corporation. All rights reserved.
 
  PrismShell.wxs
 
  D:\Builds\PRISM XP\Build 11.51.\Binlight -v PrismShell.wixobj
  Microsoft (R) Windows Installer Xml Linker version 3.0.5217.0
  Copyright (C) Microsoft Corporation. All rights reserved.
 
  Updating file information.
  Creating cabinet files.
  Creating cabinet
  'C:\Users\roy\AppData\Local\Temp\jyewbz0r\#MergeModule.CABinet'.
  Generating database.
  D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(18) : error
  LGHT0130 : The primary key 'reg0387C011F3F8A22BDFC14B
  72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918' is duplicated in
  table
  'Registry'.  Please remove one of the entries or
   rename a part of the primary key to avoid the collision.
 
  My merge module looks like this:
 
  ?xml version=1.0 encoding=utf-8?
  Wix xmlns:wi=http://schemas.microsoft.com/wix/2006/wi;
  xmlns=http://schemas.microsoft.com/wix/2006/wi;
Module Id=PrismShell Language=1033 Version=1.0.0.0
  Package Id=C7AC8538-65ED-4C2B-AE16-6291871D0918
  Description=PRISM
  Shell Module Comments=PRISM Shell Merge Module Manufacturer=Acme
  InstallerVersion=300
  /Package
  Icon Id=PRISM.ICO SourceFile=PRISM.exe
  /Icon
  Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder Name=Program Files
  Directory Id=HOCDir Name=Acme
Directory Id=INSTALLLOCATION Name=PRISM Shell
Component Id=DisplayFridayListUI.dll
  Guid={77B6CDD1-B9C6-4497-B7F5-242B9783D6A3}
File Id=DisplayFridayListUI.dll
  KeyPath=yes
  Source=SourceDir\DisplayFridayListUI.dll
TypeLib
  Id={3515D627-3FA0-490F-9330-02A73023E0C0}
  Description=DisplayFridayListUI HelpDirectory=TARGETDIR
  Language=0
  MajorVersion=1 MinorVersion=0
Class
  Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
  Context=InprocServer32
  Description=DisplayFridayListUI.CDisplayFridayList
  ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
  Id=DisplayFridayListUI.CDisplayFridayList
  Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
  Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
  Name=CDisplayFridayList
  ProxyStubClassId={00020424---C000-0046}
  ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File
RegistryValue Root=HKCR
  Key=CLSID\{9AF8DE3E

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-05-13 Thread Brian Rogers 
Hey Roy,

This is great news! Thank you for providing all the information to resolve
the bugs. I hope that this version will get you through until the next
version smile/. All further bugs will be held until feature works starts
then.

I appreciate your feedback and support while we addressed these issues.

Thanks,

Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com


On Wed, May 13, 2009 at 3:19 PM, Roy Abou Assaly royass...@gmail.comwrote:


 Yes it does.  I had to wait to update the build with the latest version due
 to other technical reasons, but after installing the latest version,
 everything worked right off the bat.  I tested with several modules and all
 the DLLs were registered.

 I also made a test installation package where I install 1 DLL and I
 monitored my application to see if the DLL was indeed registered.  It
 worked.  I did a before scenario where I basically unregistered the DLL,
 ran
 the application and saw that it complained about the missing the DLL, then
 I
 installed the test package with the DLL in question, and the application
 worked.

 So yeah...I tried to be as thorough as possible as releasing a non-working
 package is out of the question for me.  I definitely have a lot of
 confidence in Heat.

 Roy


 Brian Rogers wrote:
 
  Hey Roy,
 
  Thanks for the positive feedback and metric data!
 
  I am curious, does your installation package, once installed, work
  correctly?
 
  Thanks,
 
  Brian Rogers
  Intelligence removes complexity. - Me
  http://icumove.spaces.live.com
 
 
  On Wed, May 13, 2009 at 8:30 AM, Roy Abou Assaly
  royass...@gmail.comwrote:
 
 
  Great Work Brian!!
 
  I just incorporated WiX 3.0.5308 into our build and harvested all 128
 VB6
  COM DLLs.  Your fix works like a charm:
 
  [exec] heat.exe : warning HEAT5156 : Ignoring the registry key
  'Interface\{F3DB7AC0-A581-48C6-A973-8860578A77E1}\ProxyStubClsid/', it
  has
  already been added to the component 'EstimationEngine.dll'. The registry
  key
  value '{00020424---C000-0046}' will not be harvested.
 
  Also, here are some statistics for Heat when I harvested my 128 files:
 
  Version 3.0.4923:  WiX file produced is 25540 lines, 4.7 MB
  Version 3.0.5308:  WiX file produced is 3794 lines, 601 KB
 
  That's a great performance improvement!
 
  Thanks again for all the help.  Heat is definitely a rock solid tool.
 
  Roy
 
 
 
  Roy Abou Assaly wrote:
  
I have filed the following bug:
  
 
 https://sourceforge.net/tracker/?func=detailatid=642714aid=2783049group_id=105970
   and included test cases and the binary where you can reproduce how
  light
   is broken on the COM VB6 WiX output from Heat from version 3.0.4923 to
   3.0.5224.
  
   Please let me know if I can be of any help at all.
  
 

 --
 View this message in context:
 http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p2886906.html
 Sent from the wix-users mailing list archive at Nabble.com.



 --
 The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
 production scanning environment may not be a perfect world - but thanks to
 Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
 i700
 Series Scanner you'll get full speed at 300 dpi even with all image
 processing features enabled. http://p.sf.net/sfu/kodak-com
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-04-28 Thread Roy Abou Assaly 

I have filed the following bug: 
https://sourceforge.net/tracker/?func=detailatid=642714aid=2783049group_id=105970
and included test cases and the binary where you can reproduce how light is
broken on the COM VB6 WiX output from Heat from version 3.0.4923 to
3.0.5224.

Please let me know if I can be of any help at all.


Roy Abou Assaly wrote:
 
 Sorry.  I'll explain the situation.  I sort of cried wolf in the
 beginning since I used an XSLT to massage my XML after Heat produced the
 XML.  At that point Candle wouldn't compile.  That was my mistake as
 confirmed by Brian and yourself.  I fixed that error.  When it came to
 running Light to produce my merge module, these were my findings:
 
 In 3.0.4923 (my current build setup)
 
 1. Run Heat : OK ($heat dir d:\foo -svb6 -sfrag -suid -gg -our
 PrismShell.wxs)
 2. Run Candle: ERROR:  
 [exec] D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(180)
 : error CNDL0010 : The Class/@Server attribute was not found; it is
 required.
 
 Fixed by running a custom XSLT that added the Class/@Server attribute.
 
 3. Run Light:  OK (PrismShell.msm produced and later incorporated into an
 MSI).
 
 In 3.0.5217 and in 3.0.5224 (I'm trying to upgrade to the latest version
 of WiX)
 
 1. Run Heat: OK ($heat dir d:\foo -svb6 -sfrag -suid -gg -our
 PrismShell.wxs)
 2. Run Candle: OK
 3. Run Light:  Error:
 
  [exec] Microsoft (R) Windows Installer Xml Linker version 3.0.5217.0
  [exec] Copyright (C) Microsoft Corporation. All rights reserved.
  [exec]
  [exec] Updating file information.
  [exec] Creating cabinet files.
  [exec] Creating cabinet
 'C:\Users\assalr\AppData\Local\Temp\fkjhmoud\#MergeModule.CABinet'.
  [exec] Generating database.
  [exec] D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(19) :
 error LGHT0130 : The primary key
 'reg0387C011F3F8A22BDFC14B72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918'
 is duplicated in table 'Registry'.  Please remove one of the entries or
 rename a part of the primary key to avoid the collision.
 
 The WiX XML that is generating the above error looks like the same that
 you had generated before:
 
 Component Id=DisplayFridayListUI.dll
 Guid={821C19F9-E65C-48D5-BF11-07F593D7839B}
   File Id=DisplayFridayListUI.dll KeyPath=yes
 Source=SourceDir\DisplayFridayListUI.dll
   TypeLib Id={3515D627-3FA0-490F-9330-02A73023E0C0}
 Description=DisplayFridayListUI HelpDirectory=PRISMMsi Language=0
 MajorVersion=1 MinorVersion=0
   Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
 Context=InprocServer32
 Description=DisplayFridayListUI.CDisplayFridayList
 ThreadingModel=apartment Version=1.0 Programmable=yes
   ProgId 
 Id=DisplayFridayListUI.CDisplayFridayList
 Description=DisplayFridayListUI.CDisplayFridayList /
   /Class
   Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
 Name=CDisplayFridayList
 ProxyStubClassId={00020424---C000-0046}
 ProxyStubClassId32={00020424---C000-0046} /
   /TypeLib
   /File
   RegistryValue Root=HKCR
 Key=CLSID\{9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}\Implemented
 Categories\{40FC6ED5-2438-11CF-A3DB-080036F12502} Value= Type=string
 Action=write /
   RegistryValue Root=HKCR
 Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid
 Value={00020424---C000-0046} Type=string
 Action=write /
   RegistryValue Root=HKCR
 Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid32
 Value={00020424---C000-0046} Type=string
 Action=write /
   RegistryValue Root=HKCR
 Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
 Value=_CDisplayFridayList Type=string Action=write /
 /Component
 
 Yes, it compiles, but it's not linking with Light.
 
 This is where I am right now.  Please note that the XML that Heat produces
 in 3.0.4923 is much, much bigger than in 3.0.5217 and 3.0.5224.  Let me
 know if you need me to send you a binary (DisplayFridayListUI.dll) that
 can reproduce this.
 
 If I can't resolve this issue, I'm afraid I will have to stick with
 3.0.4923 as 3.0.5224 has a break that I can't work around.
 
 If anything is unclear, let me know.  Thanks again,
 
 Roy
 
 
 Neil Sleightholm wrote:
 
 I am not sure I understand what you are asking, could you explain?
 
 Neil
 
 -Original Message-
 From: Roy Abou Assaly [mailto:royass...@gmail.com] 
 Sent: 24 April 2009 16:02
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
 
 
 Can anyone run light 3.0.5217 on this to confirm this?  The merge module
 simple won't build and that Interface element is indeed needed.
 
 Thanks again.
 
 
 Roy Abou Assaly wrote:
 
 Oh, and one more:
 
 00020420---C000-0046
 
 After that, I was able to build my merge module and link them and
 create
 my MSI which contains 129 vb6 com DLLs and various OCXs

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-04-27 Thread Roy Abou Assaly 

Sorry.  I'll explain the situation.  I sort of cried wolf in the beginning
since I used an XSLT to massage my XML after Heat produced the XML.  At that
point Candle wouldn't compile.  That was my mistake as confirmed by Brian
and yourself.  I fixed that error.  When it came to running Light to produce
my merge module, these were my findings:

In 3.0.4923 (my current build setup)

1. Run Heat : OK ($heat dir d:\foo -svb6 -sfrag -suid -gg -our
PrismShell.wxs)
2. Run Candle: ERROR:  
[exec] D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(180) :
error CNDL0010 : The Class/@Server attribute was not found; it is required.

Fixed by running a custom XSLT that added the Class/@Server attribute.

3. Run Light:  OK (PrismShell.msm produced and later incorporated into an
MSI).

In 3.0.5217 and in 3.0.5224 (I'm trying to upgrade to the latest version of
WiX)

1. Run Heat: OK ($heat dir d:\foo -svb6 -sfrag -suid -gg -our
PrismShell.wxs)
2. Run Candle: OK
3. Run Light:  Error:

 [exec] Microsoft (R) Windows Installer Xml Linker version 3.0.5217.0
 [exec] Copyright (C) Microsoft Corporation. All rights reserved.
 [exec]
 [exec] Updating file information.
 [exec] Creating cabinet files.
 [exec] Creating cabinet
'C:\Users\assalr\AppData\Local\Temp\fkjhmoud\#MergeModule.CABinet'.
 [exec] Generating database.
 [exec] D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(19) :
error LGHT0130 : The primary key
'reg0387C011F3F8A22BDFC14B72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918'
is duplicated in table 'Registry'.  Please remove one of the entries or
rename a part of the primary key to avoid the collision.

The WiX XML that is generating the above error looks like the same that you
had generated before:

Component Id=DisplayFridayListUI.dll
Guid={821C19F9-E65C-48D5-BF11-07F593D7839B}
File Id=DisplayFridayListUI.dll KeyPath=yes
Source=SourceDir\DisplayFridayListUI.dll
TypeLib Id={3515D627-3FA0-490F-9330-02A73023E0C0}
Description=DisplayFridayListUI HelpDirectory=PRISMMsi Language=0
MajorVersion=1 MinorVersion=0
Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId 
Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File
RegistryValue Root=HKCR
Key=CLSID\{9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}\Implemented
Categories\{40FC6ED5-2438-11CF-A3DB-080036F12502} Value= Type=string
Action=write /
RegistryValue Root=HKCR
Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid
Value={00020424---C000-0046} Type=string Action=write
/
RegistryValue Root=HKCR
Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid32
Value={00020424---C000-0046} Type=string Action=write
/
RegistryValue Root=HKCR
Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Value=_CDisplayFridayList Type=string Action=write /
/Component

Yes, it compiles, but it's not linking with Light.

This is where I am right now.  Please note that the XML that Heat produces
in 3.0.4923 is much, much bigger than in 3.0.5217 and 3.0.5224.  Let me know
if you need me to send you a binary (DisplayFridayListUI.dll) that can
reproduce this.

If I can't resolve this issue, I'm afraid I will have to stick with 3.0.4923
as 3.0.5224 has a break that I can't work around.

If anything is unclear, let me know.  Thanks again,

Roy


Neil Sleightholm wrote:
 
 I am not sure I understand what you are asking, could you explain?
 
 Neil
 
 -Original Message-
 From: Roy Abou Assaly [mailto:royass...@gmail.com] 
 Sent: 24 April 2009 16:02
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
 
 
 Can anyone run light 3.0.5217 on this to confirm this?  The merge module
 simple won't build and that Interface element is indeed needed.
 
 Thanks again.
 
 
 Roy Abou Assaly wrote:
 
 Oh, and one more:
 
 00020420---C000-0046
 
 After that, I was able to build my merge module and link them and
 create
 my MSI which contains 129 vb6 com DLLs and various OCXs.  Again, my
 experience in this area is weak, but the product seems to install and
 uninstall without issues even though I remove those elements that I
 didn't
 fully understand.
 
 So I went and test the application, and of course, it threw an error
 saying the Interface isn't registered, which makes sense since I
 removed
 them.  So my ignorance has cost me.  I really need those interface
 elements or else

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-04-24 Thread Roy Abou Assaly 

Can anyone run light 3.0.5217 on this to confirm this?  The merge module
simple won't build and that Interface element is indeed needed.

Thanks again.


Roy Abou Assaly wrote:
 
 Oh, and one more:
 
 00020420---C000-0046
 
 After that, I was able to build my merge module and link them and create
 my MSI which contains 129 vb6 com DLLs and various OCXs.  Again, my
 experience in this area is weak, but the product seems to install and
 uninstall without issues even though I remove those elements that I didn't
 fully understand.
 
 So I went and test the application, and of course, it threw an error
 saying the Interface isn't registered, which makes sense since I removed
 them.  So my ignorance has cost me.  I really need those interface
 elements or else the application won't work.
 
 
 Roy Abou Assaly wrote:
 
 Still kind of stuck.  I was able to generate the exact xml as Brian did. 
 Candle compiled fine, but light is complaining.  I'm trying to generate a
 merge module out of it.  Getting this error:
 
  [exec] D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(18) :
 error LGHT0130 : The primary key 'reg0387C011F3
 F8A22BDFC14B72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918' is
 duplicated in table 'Registry'.  Please remove one of the entries or
 rename a part of the primary key to avoid the collision.
 
 D:\Builds\PRISM XP\Build 11.51.\Bincandle -v PrismShell.wxs
 Microsoft (R) Windows Installer Xml Compiler version 3.0.5217.0
 Copyright (C) Microsoft Corporation. All rights reserved.
 
 PrismShell.wxs
 
 D:\Builds\PRISM XP\Build 11.51.\Binlight -v PrismShell.wixobj
 Microsoft (R) Windows Installer Xml Linker version 3.0.5217.0
 Copyright (C) Microsoft Corporation. All rights reserved.
 
 Updating file information.
 Creating cabinet files.
 Creating cabinet
 'C:\Users\roy\AppData\Local\Temp\jyewbz0r\#MergeModule.CABinet'.
 Generating database.
 D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(18) : error
 LGHT0130 : The primary key 'reg0387C011F3F8A22BDFC14B
 72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918' is duplicated in table
 'Registry'.  Please remove one of the entries or
  rename a part of the primary key to avoid the collision.
 
 My merge module looks like this:
 
 ?xml version=1.0 encoding=utf-8?
 Wix xmlns:wi=http://schemas.microsoft.com/wix/2006/wi;
 xmlns=http://schemas.microsoft.com/wix/2006/wi;
   Module Id=PrismShell Language=1033 Version=1.0.0.0
 Package Id=C7AC8538-65ED-4C2B-AE16-6291871D0918 Description=PRISM
 Shell Module Comments=PRISM Shell Merge Module Manufacturer=Acme
 InstallerVersion=300
 /Package
 Icon Id=PRISM.ICO SourceFile=PRISM.exe
 /Icon
 Directory Id=TARGETDIR Name=SourceDir
   Directory Id=ProgramFilesFolder Name=Program Files
 Directory Id=HOCDir Name=Acme
   Directory Id=INSTALLLOCATION Name=PRISM Shell
  Component Id=DisplayFridayListUI.dll
 Guid={77B6CDD1-B9C6-4497-B7F5-242B9783D6A3}
  File Id=DisplayFridayListUI.dll KeyPath=yes
 Source=SourceDir\DisplayFridayListUI.dll
  TypeLib 
 Id={3515D627-3FA0-490F-9330-02A73023E0C0}
 Description=DisplayFridayListUI HelpDirectory=TARGETDIR Language=0
 MajorVersion=1 MinorVersion=0
  Class 
 Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
 Context=InprocServer32
 Description=DisplayFridayListUI.CDisplayFridayList
 ThreadingModel=apartment Version=1.0 Programmable=yes
  ProgId 
 Id=DisplayFridayListUI.CDisplayFridayList
 Description=DisplayFridayListUI.CDisplayFridayList /
  /Class
  Interface 
 Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
 Name=CDisplayFridayList
 ProxyStubClassId={00020424---C000-0046}
 ProxyStubClassId32={00020424---C000-0046} /
  /TypeLib
  /File
  RegistryValue Root=HKCR
 Key=CLSID\{9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}\Implemented
 Categories\{40FC6ED5-2438-11CF-A3DB-080036F12502} Value= Type=string
 Action=write /
  RegistryValue Root=HKCR
 Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid
 Value={00020424---C000-0046} Type=string
 Action=write /
  RegistryValue Root=HKCR
 Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid32
 Value={00020424---C000-0046} Type=string
 Action=write /
  RegistryValue Root=HKCR
 Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
 Value=_CDisplayFridayList Type=string Action=write /
  /Component
 
   /Directory
 /Directory
   /Directory
   Directory Id=ProgramMenuFolder Name=Programs
 Directory

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-04-24 Thread Neil Sleightholm 
I am not sure I understand what you are asking, could you explain?

Neil

-Original Message-
From: Roy Abou Assaly [mailto:royass...@gmail.com] 
Sent: 24 April 2009 16:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output


Can anyone run light 3.0.5217 on this to confirm this?  The merge module
simple won't build and that Interface element is indeed needed.

Thanks again.


Roy Abou Assaly wrote:
 
 Oh, and one more:
 
 00020420---C000-0046
 
 After that, I was able to build my merge module and link them and
create
 my MSI which contains 129 vb6 com DLLs and various OCXs.  Again, my
 experience in this area is weak, but the product seems to install and
 uninstall without issues even though I remove those elements that I
didn't
 fully understand.
 
 So I went and test the application, and of course, it threw an error
 saying the Interface isn't registered, which makes sense since I
removed
 them.  So my ignorance has cost me.  I really need those interface
 elements or else the application won't work.
 
 
 Roy Abou Assaly wrote:
 
 Still kind of stuck.  I was able to generate the exact xml as Brian
did. 
 Candle compiled fine, but light is complaining.  I'm trying to
generate a
 merge module out of it.  Getting this error:
 
  [exec] D:\Builds\PRISM XP\Build
11.51.\Bin\PrismShell.wxs(18) :
 error LGHT0130 : The primary key 'reg0387C011F3
 F8A22BDFC14B72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918' is
 duplicated in table 'Registry'.  Please remove one of the entries or
 rename a part of the primary key to avoid the collision.
 
 D:\Builds\PRISM XP\Build 11.51.\Bincandle -v PrismShell.wxs
 Microsoft (R) Windows Installer Xml Compiler version 3.0.5217.0
 Copyright (C) Microsoft Corporation. All rights reserved.
 
 PrismShell.wxs
 
 D:\Builds\PRISM XP\Build 11.51.\Binlight -v PrismShell.wixobj
 Microsoft (R) Windows Installer Xml Linker version 3.0.5217.0
 Copyright (C) Microsoft Corporation. All rights reserved.
 
 Updating file information.
 Creating cabinet files.
 Creating cabinet
 'C:\Users\roy\AppData\Local\Temp\jyewbz0r\#MergeModule.CABinet'.
 Generating database.
 D:\Builds\PRISM XP\Build 11.51.\Bin\PrismShell.wxs(18) : error
 LGHT0130 : The primary key 'reg0387C011F3F8A22BDFC14B
 72466D9C9A.C7AC8538_65ED_4C2B_AE16_6291871D0918' is duplicated in
table
 'Registry'.  Please remove one of the entries or
  rename a part of the primary key to avoid the collision.
 
 My merge module looks like this:
 
 ?xml version=1.0 encoding=utf-8?
 Wix xmlns:wi=http://schemas.microsoft.com/wix/2006/wi;
 xmlns=http://schemas.microsoft.com/wix/2006/wi;
   Module Id=PrismShell Language=1033 Version=1.0.0.0
 Package Id=C7AC8538-65ED-4C2B-AE16-6291871D0918
Description=PRISM
 Shell Module Comments=PRISM Shell Merge Module Manufacturer=Acme
 InstallerVersion=300
 /Package
 Icon Id=PRISM.ICO SourceFile=PRISM.exe
 /Icon
 Directory Id=TARGETDIR Name=SourceDir
   Directory Id=ProgramFilesFolder Name=Program Files
 Directory Id=HOCDir Name=Acme
   Directory Id=INSTALLLOCATION Name=PRISM Shell
  Component Id=DisplayFridayListUI.dll
 Guid={77B6CDD1-B9C6-4497-B7F5-242B9783D6A3}
  File Id=DisplayFridayListUI.dll
KeyPath=yes
 Source=SourceDir\DisplayFridayListUI.dll
  TypeLib
Id={3515D627-3FA0-490F-9330-02A73023E0C0}
 Description=DisplayFridayListUI HelpDirectory=TARGETDIR
Language=0
 MajorVersion=1 MinorVersion=0
  Class
Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
 Context=InprocServer32
 Description=DisplayFridayListUI.CDisplayFridayList
 ThreadingModel=apartment Version=1.0 Programmable=yes
  ProgId
Id=DisplayFridayListUI.CDisplayFridayList
 Description=DisplayFridayListUI.CDisplayFridayList /
  /Class
  Interface
Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
 Name=CDisplayFridayList
 ProxyStubClassId={00020424---C000-0046}
 ProxyStubClassId32={00020424---C000-0046} /
  /TypeLib
  /File
  RegistryValue Root=HKCR
 Key=CLSID\{9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}\Implemented
 Categories\{40FC6ED5-2438-11CF-A3DB-080036F12502} Value=
Type=string
 Action=write /
  RegistryValue Root=HKCR
 Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid
 Value={00020424---C000-0046} Type=string
 Action=write /
  RegistryValue Root=HKCR

Key=Interface\{2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}\ProxyStubClsid32
 Value={00020424---C000-0046} Type=string
 Action=write /
  RegistryValue Root=HKCR
 Key=Interface

[WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-04-23 Thread Roy Abou Assaly 

Hi,

In 3.0.4923, I used to get the following output (note how the Interface
element is *outside* of the File element):

Component Id=DisplayFridayListUI.dll
Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
  File Id=DisplayFridayListUI.dll
Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
Server=DisplayFridayListUI.dll ThreadingModel=apartment Version=1.0
  ProgId Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList
  /ProgId
/Class
  /File
  Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046}
  /Interface


In 3.0.5217, the heat output is (note how the Interface element is *inside*
the File element):

Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
Context=InprocServer32 Description=VBPropertyBag
ThreadingModel=apartment ForeignServer=msvbvm60.dll /
File Id=filA79D608464525B697087B7D7200AF704
KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
TypeLib Id={3515D627-3FA0-490F-9330-02A73023E0C0}
Description=DisplayFridayListUI
HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
MajorVersion=1 MinorVersion=0
Class
Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
Description=DisplayFridayListUI.CDisplayFridayList
ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
Id=DisplayFridayListUI.CDisplayFridayList
Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
ProxyStubClassId={00020424---C000-0046}
ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File

Using the -svb6 doesn't change anything.  When using Candle to compile, I
get the following error:

error CNDL0005 : The File element contains an unexpected child element
'Interface'.

This wasn't the case before.  Should I file a bug?  I'm sure you're starting
to hate my constant emails regarding vb6 and heat :)




-- 
View this message in context: 
http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p2686239.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;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] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-04-23 Thread Brian Rogers 
Roy,

One question on this however. From the code you sent the Interface /
element is actually under the TypeLib / which is legal. Are you sure that
it is that actual line and not some where else?

Thanks,

Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com


On Thu, Apr 23, 2009 at 2:07 PM, Brian Rogers rogers.br...@gmail.comwrote:

 Hey Roy,

 Please file a bug.

 Thanks,

 Brian Rogers
 Intelligence removes complexity. - Me
 http://icumove.spaces.live.com



 On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly royass...@gmail.comwrote:


 Hi,

 In 3.0.4923, I used to get the following output (note how the Interface
 element is *outside* of the File element):

Component Id=DisplayFridayListUI.dll
 Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
  File Id=DisplayFridayListUI.dll
 Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
 XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
 Context=InprocServer32
 Description=DisplayFridayListUI.CDisplayFridayList
 Server=DisplayFridayListUI.dll ThreadingModel=apartment Version=1.0
  ProgId Id=DisplayFridayListUI.CDisplayFridayList
 Description=DisplayFridayListUI.CDisplayFridayList
  /ProgId
/Class
  /File
  Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
 Name=CDisplayFridayList
 ProxyStubClassId={00020424---C000-0046}
 ProxyStubClassId32={00020424---C000-0046}
  /Interface


 In 3.0.5217, the heat output is (note how the Interface element is
 *inside*
 the File element):

Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
 Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
 Context=InprocServer32 Description=VBPropertyBag
 ThreadingModel=apartment ForeignServer=msvbvm60.dll /
File Id=filA79D608464525B697087B7D7200AF704
 KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
TypeLib
 Id={3515D627-3FA0-490F-9330-02A73023E0C0}
 Description=DisplayFridayListUI
 HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
 MajorVersion=1 MinorVersion=0
Class
 Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
 Description=DisplayFridayListUI.CDisplayFridayList
 ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
 Id=DisplayFridayListUI.CDisplayFridayList
 Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
 Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
 ProxyStubClassId={00020424---C000-0046}
 ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File

 Using the -svb6 doesn't change anything.  When using Candle to compile, I
 get the following error:

 error CNDL0005 : The File element contains an unexpected child element
 'Interface'.

 This wasn't the case before.  Should I file a bug?  I'm sure you're
 starting
 to hate my constant emails regarding vb6 and heat :)




 --
 View this message in context:
 http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p2686239.html
 Sent from the wix-users mailing list archive at Nabble.com.



 --
 Crystal Reports #45; New Free Runtime and 30 Day Trial
 Check out the new simplified licensign option that enables unlimited
 royalty#45;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



--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;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] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-04-23 Thread Roy Abou Assaly 


Hi Brian,

The bug is: 
https://sourceforge.net/tracker/?func=detailaid=2779893group_id=105970atid=642714
I've attached a DLL you can use to test with in case you don't have one to
reproduce the issue.

Thanks!

Roy


Brian Rogers wrote:
 
 Hey Roy,
 
 Please file a bug.
 
 Thanks,
 
 Brian Rogers
 Intelligence removes complexity. - Me
 http://icumove.spaces.live.com
 
 
 On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly
 royass...@gmail.comwrote:
 

 Hi,

 In 3.0.4923, I used to get the following output (note how the Interface
 element is *outside* of the File element):

Component Id=DisplayFridayListUI.dll
 Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
  File Id=DisplayFridayListUI.dll
 Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
 XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
 Context=InprocServer32
 Description=DisplayFridayListUI.CDisplayFridayList
 Server=DisplayFridayListUI.dll ThreadingModel=apartment
 Version=1.0
  ProgId Id=DisplayFridayListUI.CDisplayFridayList
 Description=DisplayFridayListUI.CDisplayFridayList
  /ProgId
/Class
  /File
  Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
 Name=CDisplayFridayList
 ProxyStubClassId={00020424---C000-0046}
 ProxyStubClassId32={00020424---C000-0046}
  /Interface


 In 3.0.5217, the heat output is (note how the Interface element is
 *inside*
 the File element):

Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
 Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
 Context=InprocServer32 Description=VBPropertyBag
 ThreadingModel=apartment ForeignServer=msvbvm60.dll /
File Id=filA79D608464525B697087B7D7200AF704
 KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
TypeLib
 Id={3515D627-3FA0-490F-9330-02A73023E0C0}
 Description=DisplayFridayListUI
 HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
 MajorVersion=1 MinorVersion=0
Class
 Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
 Description=DisplayFridayListUI.CDisplayFridayList
 ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
 Id=DisplayFridayListUI.CDisplayFridayList
 Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
 Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
 ProxyStubClassId={00020424---C000-0046}
 ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File

 Using the -svb6 doesn't change anything.  When using Candle to compile, I
 get the following error:

 error CNDL0005 : The File element contains an unexpected child element
 'Interface'.

 This wasn't the case before.  Should I file a bug?  I'm sure you're
 starting
 to hate my constant emails regarding vb6 and heat :)




 --
 View this message in context:
 http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p2686239.html
 Sent from the wix-users mailing list archive at Nabble.com.



 --
 Crystal Reports #45; New Free Runtime and 30 Day Trial
 Check out the new simplified licensign option that enables unlimited
 royalty#45;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

 --
 Crystal Reports #45; New Free Runtime and 30 Day Trial
 Check out the new simplified licensign option that enables unlimited
 royalty#45;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
 
 

-- 
View this message in context: 
http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p2686605.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;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

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-04-23 Thread Neil Sleightholm 
Roy

The interface element is inside the TypeLib element, I have just
checked my code and this is valid and has been the same for a while, so
the error doesn't really make sense. When you raise a bug is it possible
to include the DLL you are scanning?

Neil

-Original Message-
From: Brian Rogers [mailto:rogers.br...@gmail.com] 
Sent: 23 April 2009 22:07
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

Hey Roy,

Please file a bug.

Thanks,

Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com


On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly
royass...@gmail.comwrote:


 Hi,

 In 3.0.4923, I used to get the following output (note how the
Interface
 element is *outside* of the File element):

Component Id=DisplayFridayListUI.dll
 Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
  File Id=DisplayFridayListUI.dll
 Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
 XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
 Context=InprocServer32
 Description=DisplayFridayListUI.CDisplayFridayList
 Server=DisplayFridayListUI.dll ThreadingModel=apartment
Version=1.0
  ProgId Id=DisplayFridayListUI.CDisplayFridayList
 Description=DisplayFridayListUI.CDisplayFridayList
  /ProgId
/Class
  /File
  Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
 Name=CDisplayFridayList
 ProxyStubClassId={00020424---C000-0046}
 ProxyStubClassId32={00020424---C000-0046}
  /Interface


 In 3.0.5217, the heat output is (note how the Interface element is
*inside*
 the File element):

Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
 Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
 Context=InprocServer32 Description=VBPropertyBag
 ThreadingModel=apartment ForeignServer=msvbvm60.dll /
File Id=filA79D608464525B697087B7D7200AF704
 KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
TypeLib
Id={3515D627-3FA0-490F-9330-02A73023E0C0}
 Description=DisplayFridayListUI
 HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
 MajorVersion=1 MinorVersion=0
Class
 Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
 Description=DisplayFridayListUI.CDisplayFridayList
 ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
 Id=DisplayFridayListUI.CDisplayFridayList
 Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
 Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
 ProxyStubClassId={00020424---C000-0046}
 ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File

 Using the -svb6 doesn't change anything.  When using Candle to
compile, I
 get the following error:

 error CNDL0005 : The File element contains an unexpected child element
 'Interface'.

 This wasn't the case before.  Should I file a bug?  I'm sure you're
 starting
 to hate my constant emails regarding vb6 and heat :)




 --
 View this message in context:

http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p
2686239.html
 Sent from the wix-users mailing list archive at Nabble.com.





--
 Crystal Reports #45; New Free Runtime and 30 Day Trial
 Check out the new simplified licensign option that enables unlimited
 royalty#45;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


--
Crystal Reports #45; New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty#45;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

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

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-04-23 Thread Neil Sleightholm 
Running heat and candle against the file you attached to the bug doesn't
generate the error you reported could you give more details of the
command lines you are using?

Neil

-Original Message-
From: Roy Abou Assaly [mailto:royass...@gmail.com] 
Sent: 23 April 2009 22:18
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output



Hi Brian,

The bug is: 
https://sourceforge.net/tracker/?func=detailaid=2779893group_id=105970
atid=642714
I've attached a DLL you can use to test with in case you don't have one
to
reproduce the issue.

Thanks!

Roy


Brian Rogers wrote:
 
 Hey Roy,
 
 Please file a bug.
 
 Thanks,
 
 Brian Rogers
 Intelligence removes complexity. - Me
 http://icumove.spaces.live.com
 
 
 On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly
 royass...@gmail.comwrote:
 

 Hi,

 In 3.0.4923, I used to get the following output (note how the
Interface
 element is *outside* of the File element):

Component Id=DisplayFridayListUI.dll
 Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
  File Id=DisplayFridayListUI.dll
 Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
 XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
 Context=InprocServer32
 Description=DisplayFridayListUI.CDisplayFridayList
 Server=DisplayFridayListUI.dll ThreadingModel=apartment
 Version=1.0
  ProgId Id=DisplayFridayListUI.CDisplayFridayList
 Description=DisplayFridayListUI.CDisplayFridayList
  /ProgId
/Class
  /File
  Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
 Name=CDisplayFridayList
 ProxyStubClassId={00020424---C000-0046}
 ProxyStubClassId32={00020424---C000-0046}
  /Interface


 In 3.0.5217, the heat output is (note how the Interface element is
 *inside*
 the File element):

Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
 Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
 Context=InprocServer32 Description=VBPropertyBag
 ThreadingModel=apartment ForeignServer=msvbvm60.dll /
File Id=filA79D608464525B697087B7D7200AF704
 KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
TypeLib
 Id={3515D627-3FA0-490F-9330-02A73023E0C0}
 Description=DisplayFridayListUI
 HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
 MajorVersion=1 MinorVersion=0
Class
 Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
 Description=DisplayFridayListUI.CDisplayFridayList
 ThreadingModel=apartment Version=1.0 Programmable=yes
ProgId
 Id=DisplayFridayListUI.CDisplayFridayList
 Description=DisplayFridayListUI.CDisplayFridayList /
/Class
Interface
 Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
 ProxyStubClassId={00020424---C000-0046}
 ProxyStubClassId32={00020424---C000-0046} /
/TypeLib
/File

 Using the -svb6 doesn't change anything.  When using Candle to
compile, I
 get the following error:

 error CNDL0005 : The File element contains an unexpected child
element
 'Interface'.

 This wasn't the case before.  Should I file a bug?  I'm sure you're
 starting
 to hate my constant emails regarding vb6 and heat :)




 --
 View this message in context:

http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p
2686239.html
 Sent from the wix-users mailing list archive at Nabble.com.





--
 Crystal Reports #45; New Free Runtime and 30 Day Trial
 Check out the new simplified licensign option that enables unlimited
 royalty#45;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



--
 Crystal Reports #45; New Free Runtime and 30 Day Trial
 Check out the new simplified licensign option that enables unlimited
 royalty#45;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
 
 

-- 
View this message in context:
http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p
2686605.html
Sent from the wix-users mailing list archive at Nabble.com

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-04-23 Thread Roy Abou Assaly 

Both of you are correct.  I have an XSLT that massage the XML that heat
generates in order to ensure certain shortcuts are added and changes a few
other things as well.  In the process, the XSLT is not doing its job.  I
would cancel the bug as it looks like like it's a data issue on my end.

Sorry for the trouble.

On Thu, Apr 23, 2009 at 5:39 PM, Neil Sleightholm (via Nabble) 
ml-user+58265-122838...@n2.nabble.comml-user%2b58265-122838...@n2.nabble.com
 wrote:

 Running heat and candle against the file you attached to the bug doesn't
 generate the error you reported could you give more details of the
 command lines you are using?

 Neil

 -Original Message-
 From: Roy Abou Assaly 
 [mailto:royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=0]

 Sent: 23 April 2009 22:18
 To: 
 wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=1
 Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output



 Hi Brian,

 The bug is:
 https://sourceforge.net/tracker/?func=detailaid=2779893group_id=105970
 atid=642714
 I've attached a DLL you can use to test with in case you don't have one
 to
 reproduce the issue.

 Thanks!

 Roy


 Brian Rogers wrote:
 
  Hey Roy,
 
  Please file a bug.
 
  Thanks,
 
  Brian Rogers
  Intelligence removes complexity. - Me
  http://icumove.spaces.live.com
 
 
  On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly
  royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=2wrote:

 
 
  Hi,
 
  In 3.0.4923, I used to get the following output (note how the
 Interface
  element is *outside* of the File element):
 
 Component Id=DisplayFridayListUI.dll
  Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
   File Id=DisplayFridayListUI.dll
  Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
  XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
 Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
  Context=InprocServer32
  Description=DisplayFridayListUI.CDisplayFridayList
  Server=DisplayFridayListUI.dll ThreadingModel=apartment
  Version=1.0
   ProgId Id=DisplayFridayListUI.CDisplayFridayList
  Description=DisplayFridayListUI.CDisplayFridayList
   /ProgId
 /Class
   /File
   Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
  Name=CDisplayFridayList
  ProxyStubClassId={00020424---C000-0046}
  ProxyStubClassId32={00020424---C000-0046}
   /Interface
 
 
  In 3.0.5217, the heat output is (note how the Interface element is
  *inside*
  the File element):
 
 Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
  Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
 Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
  Context=InprocServer32 Description=VBPropertyBag
  ThreadingModel=apartment ForeignServer=msvbvm60.dll /
 File Id=filA79D608464525B697087B7D7200AF704
  KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
 TypeLib
  Id={3515D627-3FA0-490F-9330-02A73023E0C0}
  Description=DisplayFridayListUI
  HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
  MajorVersion=1 MinorVersion=0
 Class
  Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
  Description=DisplayFridayListUI.CDisplayFridayList
  ThreadingModel=apartment Version=1.0 Programmable=yes
 ProgId
  Id=DisplayFridayListUI.CDisplayFridayList
  Description=DisplayFridayListUI.CDisplayFridayList /
 /Class
 Interface
  Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
  ProxyStubClassId={00020424---C000-0046}
  ProxyStubClassId32={00020424---C000-0046} /
 /TypeLib
 /File
 
  Using the -svb6 doesn't change anything.  When using Candle to
 compile, I
  get the following error:
 
  error CNDL0005 : The File element contains an unexpected child
 element
  'Interface'.
 
  This wasn't the case before.  Should I file a bug?  I'm sure you're
  starting
  to hate my constant emails regarding vb6 and heat :)
 
 
 
 
  --
  View this message in context:
 
 http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p
 2686239.html
  Sent from the wix-users mailing list archive at Nabble.com.
 
 
 
 
 
 --
  Crystal Reports - New Free Runtime and 30 Day Trial
  Check out the new simplified licensign 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-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=3
  https

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-04-23 Thread Roy Abou Assaly 
 at this for too long.

Roy



Roy Abou Assaly wrote:
 
 Both of you are correct.  I have an XSLT that massage the XML that heat
 generates in order to ensure certain shortcuts are added and changes a few
 other things as well.  In the process, the XSLT is not doing its job.  I
 would cancel the bug as it looks like like it's a data issue on my end.
 
 Sorry for the trouble.
 
 On Thu, Apr 23, 2009 at 5:39 PM, Neil Sleightholm (via Nabble) 
 ml-user+58265-122838...@n2.nabble.comml-user%2b58265-122838...@n2.nabble.com
 wrote:
 
 Running heat and candle against the file you attached to the bug doesn't
 generate the error you reported could you give more details of the
 command lines you are using?

 Neil

 -Original Message-
 From: Roy Abou Assaly
 [mailto:royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=0]

 Sent: 23 April 2009 22:18
 To:
 wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=1
 Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output



 Hi Brian,

 The bug is:
 https://sourceforge.net/tracker/?func=detailaid=2779893group_id=105970
 atid=642714
 I've attached a DLL you can use to test with in case you don't have one
 to
 reproduce the issue.

 Thanks!

 Roy


 Brian Rogers wrote:
 
  Hey Roy,
 
  Please file a bug.
 
  Thanks,
 
  Brian Rogers
  Intelligence removes complexity. - Me
  http://icumove.spaces.live.com
 
 
  On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly
 
 royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=2wrote:

 
 
  Hi,
 
  In 3.0.4923, I used to get the following output (note how the
 Interface
  element is *outside* of the File element):
 
 Component Id=DisplayFridayListUI.dll
  Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
   File Id=DisplayFridayListUI.dll
  Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
  XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
 Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
  Context=InprocServer32
  Description=DisplayFridayListUI.CDisplayFridayList
  Server=DisplayFridayListUI.dll ThreadingModel=apartment
  Version=1.0
   ProgId Id=DisplayFridayListUI.CDisplayFridayList
  Description=DisplayFridayListUI.CDisplayFridayList
   /ProgId
 /Class
   /File
   Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
  Name=CDisplayFridayList
  ProxyStubClassId={00020424---C000-0046}
  ProxyStubClassId32={00020424---C000-0046}
   /Interface
 
 
  In 3.0.5217, the heat output is (note how the Interface element is
  *inside*
  the File element):
 
 Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
  Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
 Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
  Context=InprocServer32 Description=VBPropertyBag
  ThreadingModel=apartment ForeignServer=msvbvm60.dll /
 File Id=filA79D608464525B697087B7D7200AF704
  KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
 TypeLib
  Id={3515D627-3FA0-490F-9330-02A73023E0C0}
  Description=DisplayFridayListUI
  HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
  MajorVersion=1 MinorVersion=0
 Class
  Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
  Description=DisplayFridayListUI.CDisplayFridayList
  ThreadingModel=apartment Version=1.0 Programmable=yes
 ProgId
  Id=DisplayFridayListUI.CDisplayFridayList
  Description=DisplayFridayListUI.CDisplayFridayList /
 /Class
 Interface
  Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
  ProxyStubClassId={00020424---C000-0046}
  ProxyStubClassId32={00020424---C000-0046} /
 /TypeLib
 /File
 
  Using the -svb6 doesn't change anything.  When using Candle to
 compile, I
  get the following error:
 
  error CNDL0005 : The File element contains an unexpected child
 element
  'Interface'.
 
  This wasn't the case before.  Should I file a bug?  I'm sure you're
  starting
  to hate my constant emails regarding vb6 and heat :)
 
 
 
 
  --
  View this message in context:
 
 http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p
 2686239.html
  Sent from the wix-users mailing list archive at Nabble.com.
 
 
 
 
 
 --
  Crystal Reports - New Free Runtime and 30 Day Trial
  Check out the new simplified licensign 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-us...@...http://n2.nabble.com/user

Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output

2009-04-23 Thread Roy Abou Assaly 
-0046} /
 
 I then check my cleanup XSLT which I used to use to clean up the messy vb6
 output, and realized that I used to remove any element with the following
 attribute:
 
 000204EF---C000-0046
 
 compare that to:
 
 00020424---C000-0046
 
 Which is slightly off.  Me thinks I should also add this to the cleanup
 xslt file.
 
 You can copy paste it and try it out.  I'm a bit stuck.  Perhaps I've been
 staring at this for too long.
 
 Roy
 
 
 
 Roy Abou Assaly wrote:
 
 Both of you are correct.  I have an XSLT that massage the XML that heat
 generates in order to ensure certain shortcuts are added and changes a
 few
 other things as well.  In the process, the XSLT is not doing its job.  I
 would cancel the bug as it looks like like it's a data issue on my end.
 
 Sorry for the trouble.
 
 On Thu, Apr 23, 2009 at 5:39 PM, Neil Sleightholm (via Nabble) 
 ml-user+58265-122838...@n2.nabble.comml-user%2b58265-122838...@n2.nabble.com
 wrote:
 
 Running heat and candle against the file you attached to the bug doesn't
 generate the error you reported could you give more details of the
 command lines you are using?

 Neil

 -Original Message-
 From: Roy Abou Assaly
 [mailto:royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=0]

 Sent: 23 April 2009 22:18
 To:
 wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=1
 Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output



 Hi Brian,

 The bug is:
 https://sourceforge.net/tracker/?func=detailaid=2779893group_id=105970
 atid=642714
 I've attached a DLL you can use to test with in case you don't have one
 to
 reproduce the issue.

 Thanks!

 Roy


 Brian Rogers wrote:
 
  Hey Roy,
 
  Please file a bug.
 
  Thanks,
 
  Brian Rogers
  Intelligence removes complexity. - Me
  http://icumove.spaces.live.com
 
 
  On Thu, Apr 23, 2009 at 1:31 PM, Roy Abou Assaly
 
 royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2686897i=2wrote:

 
 
  Hi,
 
  In 3.0.4923, I used to get the following output (note how the
 Interface
  element is *outside* of the File element):
 
 Component Id=DisplayFridayListUI.dll
  Guid={C4773BDF-6383-423D-BB34-BBB961BFD6DF}
   File Id=DisplayFridayListUI.dll
  Name=DisplayFridayListUI.dll KeyPath=yes Source=D:\Builds\PRISM
  XP\Build 11.50.\Bin\PRISMMsi\DisplayFridayListUI.dll
 Class Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9}
  Context=InprocServer32
  Description=DisplayFridayListUI.CDisplayFridayList
  Server=DisplayFridayListUI.dll ThreadingModel=apartment
  Version=1.0
   ProgId Id=DisplayFridayListUI.CDisplayFridayList
  Description=DisplayFridayListUI.CDisplayFridayList
   /ProgId
 /Class
   /File
   Interface Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594}
  Name=CDisplayFridayList
  ProxyStubClassId={00020424---C000-0046}
  ProxyStubClassId32={00020424---C000-0046}
   /Interface
 
 
  In 3.0.5217, the heat output is (note how the Interface element is
  *inside*
  the File element):
 
 Component Id=cmp40C4F6ADC9C48FEFA7144101F481848A
  Guid={00C04661-3A43-4FD9-B484-0B27EF2BF049}
 Class Id={D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731}
  Context=InprocServer32 Description=VBPropertyBag
  ThreadingModel=apartment ForeignServer=msvbvm60.dll /
 File Id=filA79D608464525B697087B7D7200AF704
  KeyPath=yes Source=SourceDir\DisplayFridayListUI.dll
 TypeLib
  Id={3515D627-3FA0-490F-9330-02A73023E0C0}
  Description=DisplayFridayListUI
  HelpDirectory=dir667CD14ED201BFF0942A99F02E55F065 Language=0
  MajorVersion=1 MinorVersion=0
 Class
  Id={9AF8DE3E-3FFB-4F1C-AA59-3DBAB1725BB9} Context=InprocServer32
  Description=DisplayFridayListUI.CDisplayFridayList
  ThreadingModel=apartment Version=1.0 Programmable=yes
 ProgId
  Id=DisplayFridayListUI.CDisplayFridayList
  Description=DisplayFridayListUI.CDisplayFridayList /
 /Class
 Interface
  Id={2D3FD2B6-AF78-4DFD-A5C9-7CE97BC4A594} Name=CDisplayFridayList
  ProxyStubClassId={00020424---C000-0046}
  ProxyStubClassId32={00020424---C000-0046} /
 /TypeLib
 /File
 
  Using the -svb6 doesn't change anything.  When using Candle to
 compile, I
  get the following error:
 
  error CNDL0005 : The File element contains an unexpected child
 element
  'Interface'.
 
  This wasn't the case before.  Should I file a bug?  I'm sure you're
  starting
  to hate my constant emails regarding vb6 and heat :)
 
 
 
 
  --
  View this message in context:
 
 http://n2.nabble.com/Heat-3.0.4923-vs-3.0.5217-vb6-dll-output-tp2686239p
 2686239.html
  Sent from the wix-users mailing list archive at Nabble.com