Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

2009-04-17 Thread Brian Rogers 
Hey Roy,

The fix for this should be in the next drop. I appreciate the detailed
information. When you see issues like this please feel free to file a bug on
sourceforge.net/projects/wix.

Thanks,

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


On Tue, Apr 14, 2009 at 8:15 AM, Roy Abou Assaly royass...@gmail.comwrote:


 Hi,

 I was away for a week or else I would've replied sooner.  I tested the
 following using version 3.0.5210.0.

 This works:

 D:\lab\WiX\XMLEditorheat dir . -v  -sfrag -gg -svb6 -out foo.xml
 Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5210.0
 Copyright (C) Microsoft Corporation. All rights reserved.

 Trying to harvest D:\lab\WiX\XMLEditor\PRISMXMLEditor.dll as an assembly.
 Trying to harvest self-registration information from native DLL
 D:\lab\WiX\XMLEditor\PRISMXMLEditor.dll.
 Ignoring the registry key
 'Interface\{0B7F3153-C8E7-4E6D-AEBE-B6D61D78B9A3}\ProxyStubClsid/', it has
 already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
 Ignoring the registry key
 'Interface\{0B7F3153-C8E7-4E6D-AEBE-B6D61D78B9A3}\ProxyStubClsid32/', it has
 already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
 Ignoring the registry key
 'Interface\{0B7F3153-C8E7-4E6D-AEBE-B6D61D78B9A3}/', it has already been
 added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
 Ignoring the registry key
 'Interface\{1D3D80B3-86A1-4DA7-AF4B-FA12E70BB39F}\ProxyStubClsid/', it has
 already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
 Ignoring the registry key
 'Interface\{1D3D80B3-86A1-4DA7-AF4B-FA12E70BB39F}\ProxyStubClsid32/', it has
 already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
 Ignoring the registry key
 'Interface\{1D3D80B3-86A1-4DA7-AF4B-FA12E70BB39F}/', it has already been
 added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
 Ignoring the registry key
 'Interface\{399DC087-F09A-4DDE-B2A6-A3755D8506B3}\ProxyStubClsid/', it has
 already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
 Ignoring the registry key
 'Interface\{399DC087-F09A-4DDE-B2A6-A3755D8506B3}\ProxyStubClsid32/', it has
 already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
 Ignoring the registry key
 'Interface\{399DC087-F09A-4DDE-B2A6-A3755D8506B3}/', it has already been
 added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
 Ignoring the registry key
 'Interface\{EAC0509C-5990-48B8-81B3-5A2ECE581DB4}\ProxyStubClsid/', it has
 already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
 Ignoring the registry key
 'Interface\{EAC0509C-5990-48B8-81B3-5A2ECE581DB4}\ProxyStubClsid32/', it has
 already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
 Ignoring the registry key
 'Interface\{EAC0509C-5990-48B8-81B3-5A2ECE581DB4}/', it has already been
 added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.

 This gives an error:

 D:\lab\WiX\XMLEditorheat file PRISMXMLEditor.dll -v  -sfrag -gg -svb6 -out
 foo.xml
 Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5210.0
 Copyright (C) Microsoft Corporation. All rights reserved.

 heat.exe : error HEAT0001 : The path is not of a legal form.

 Exception Type: System.ArgumentException

 Stack Trace:
at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
   at System.IO.Path.NormalizePath(String path, Boolean fullCheck)
   at System.IO.Path.GetFullPathInternal(String path)
   at System.IO.Path.GetFullPath(String path)
   at
 Microsoft.Tools.WindowsInstallerXml.HarvesterCore.ResolveFilePath(String
 fileSource)
   at
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateFile(IParentElement
 parentElement, File file)
   at
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement
 parentElement, ISchemaElement element)
   at
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement
 parentElement, ISchemaElement element)
   at
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement
 parentElement, ISchemaElement element)
   at
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement
 parentElement, ISchemaElement element)
   at
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement
 parentElement, ISchemaElement element)
   at
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement
 parentElement, ISchemaElement element)
   at
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.Mutate(Wix
 wix)
at Microsoft.Tools.WindowsInstallerXml.Mutator.Mutate(Wix wix)
   at Microsoft.Tools.WindowsInstallerXml.Tools.Heat.Run(String[] args)

 I ran it with the full path and got this error which looks like it isn't
 reading the path correctly for the

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

2009-04-17 Thread Roy Abou Assaly 

Hi Brian,

I definitely will in the future.  Thanks for your all your help!

Roy

On Fri, Apr 17, 2009 at 8:57 AM, Brian Rogers (via Nabble) 
ml-user+58646-1457241...@n2.nabble.comml-user%2b58646-1457241...@n2.nabble.com
 wrote:

 Hey Roy,

 The fix for this should be in the next drop. I appreciate the detailed
 information. When you see issues like this please feel free to file a bug
 on
 sourceforge.net/projects/wix.

 Thanks,

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


 On Tue, Apr 14, 2009 at 8:15 AM, Roy Abou Assaly 
 royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2649812i=0wrote:


 
  Hi,
 
  I was away for a week or else I would've replied sooner.  I tested the
  following using version 3.0.5210.0.
 
  This works:
 
  D:\lab\WiX\XMLEditorheat dir . -v  -sfrag -gg -svb6 -out foo.xml
  Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5210.0
  Copyright (C) Microsoft Corporation. All rights reserved.
 
  Trying to harvest D:\lab\WiX\XMLEditor\PRISMXMLEditor.dll as an assembly.

  Trying to harvest self-registration information from native DLL
  D:\lab\WiX\XMLEditor\PRISMXMLEditor.dll.
  Ignoring the registry key
  'Interface\{0B7F3153-C8E7-4E6D-AEBE-B6D61D78B9A3}\ProxyStubClsid/', it
 has
  already been added to the component
 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
  Ignoring the registry key
  'Interface\{0B7F3153-C8E7-4E6D-AEBE-B6D61D78B9A3}\ProxyStubClsid32/', it
 has
  already been added to the component
 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
  Ignoring the registry key
  'Interface\{0B7F3153-C8E7-4E6D-AEBE-B6D61D78B9A3}/', it has already been
  added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
  Ignoring the registry key
  'Interface\{1D3D80B3-86A1-4DA7-AF4B-FA12E70BB39F}\ProxyStubClsid/', it
 has
  already been added to the component
 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
  Ignoring the registry key
  'Interface\{1D3D80B3-86A1-4DA7-AF4B-FA12E70BB39F}\ProxyStubClsid32/', it
 has
  already been added to the component
 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
  Ignoring the registry key
  'Interface\{1D3D80B3-86A1-4DA7-AF4B-FA12E70BB39F}/', it has already been
  added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
  Ignoring the registry key
  'Interface\{399DC087-F09A-4DDE-B2A6-A3755D8506B3}\ProxyStubClsid/', it
 has
  already been added to the component
 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
  Ignoring the registry key
  'Interface\{399DC087-F09A-4DDE-B2A6-A3755D8506B3}\ProxyStubClsid32/', it
 has
  already been added to the component
 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
  Ignoring the registry key
  'Interface\{399DC087-F09A-4DDE-B2A6-A3755D8506B3}/', it has already been
  added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
  Ignoring the registry key
  'Interface\{EAC0509C-5990-48B8-81B3-5A2ECE581DB4}\ProxyStubClsid/', it
 has
  already been added to the component
 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
  Ignoring the registry key
  'Interface\{EAC0509C-5990-48B8-81B3-5A2ECE581DB4}\ProxyStubClsid32/', it
 has
  already been added to the component
 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
  Ignoring the registry key
  'Interface\{EAC0509C-5990-48B8-81B3-5A2ECE581DB4}/', it has already been
  added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
 
  This gives an error:
 
  D:\lab\WiX\XMLEditorheat file PRISMXMLEditor.dll -v  -sfrag -gg -svb6
 -out
  foo.xml
  Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5210.0
  Copyright (C) Microsoft Corporation. All rights reserved.
 
  heat.exe : error HEAT0001 : The path is not of a legal form.
 
  Exception Type: System.ArgumentException
 
  Stack Trace:
 at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
at System.IO.Path.NormalizePath(String path, Boolean fullCheck)
at System.IO.Path.GetFullPathInternal(String path)
at System.IO.Path.GetFullPath(String path)
at
  Microsoft.Tools.WindowsInstallerXml.HarvesterCore.ResolveFilePath(String
  fileSource)
at
 
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateFile(IParentElement

  parentElement, File file)
at
 
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement

  parentElement, ISchemaElement element)
at
 
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement

  parentElement, ISchemaElement element)
at
 
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement

  parentElement, ISchemaElement element)
at
 
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement

  parentElement, ISchemaElement element)
at
 
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement

  parentElement, ISchemaElement element)
at

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

2009-04-14 Thread Roy Abou Assaly 

Hi,

I was away for a week or else I would've replied sooner.  I tested the 
following using version 3.0.5210.0.

This works:

D:\lab\WiX\XMLEditorheat dir . -v  -sfrag -gg -svb6 -out foo.xml
Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5210.0
Copyright (C) Microsoft Corporation. All rights reserved.

Trying to harvest D:\lab\WiX\XMLEditor\PRISMXMLEditor.dll as an assembly.
Trying to harvest self-registration information from native DLL 
D:\lab\WiX\XMLEditor\PRISMXMLEditor.dll.
Ignoring the registry key 
'Interface\{0B7F3153-C8E7-4E6D-AEBE-B6D61D78B9A3}\ProxyStubClsid/', it has 
already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
Ignoring the registry key 
'Interface\{0B7F3153-C8E7-4E6D-AEBE-B6D61D78B9A3}\ProxyStubClsid32/', it has 
already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
Ignoring the registry key 'Interface\{0B7F3153-C8E7-4E6D-AEBE-B6D61D78B9A3}/', 
it has already been added to the component 
'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
Ignoring the registry key 
'Interface\{1D3D80B3-86A1-4DA7-AF4B-FA12E70BB39F}\ProxyStubClsid/', it has 
already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
Ignoring the registry key 
'Interface\{1D3D80B3-86A1-4DA7-AF4B-FA12E70BB39F}\ProxyStubClsid32/', it has 
already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
Ignoring the registry key 'Interface\{1D3D80B3-86A1-4DA7-AF4B-FA12E70BB39F}/', 
it has already been added to the component 
'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
Ignoring the registry key 
'Interface\{399DC087-F09A-4DDE-B2A6-A3755D8506B3}\ProxyStubClsid/', it has 
already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
Ignoring the registry key 
'Interface\{399DC087-F09A-4DDE-B2A6-A3755D8506B3}\ProxyStubClsid32/', it has 
already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
Ignoring the registry key 'Interface\{399DC087-F09A-4DDE-B2A6-A3755D8506B3}/', 
it has already been added to the component 
'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
Ignoring the registry key 
'Interface\{EAC0509C-5990-48B8-81B3-5A2ECE581DB4}\ProxyStubClsid/', it has 
already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
Ignoring the registry key 
'Interface\{EAC0509C-5990-48B8-81B3-5A2ECE581DB4}\ProxyStubClsid32/', it has 
already been added to the component 'cmpD86DA220B5DFAFDE5B16661AC4E61230'.
Ignoring the registry key 'Interface\{EAC0509C-5990-48B8-81B3-5A2ECE581DB4}/', 
it has already been added to the component 
'cmpD86DA220B5DFAFDE5B16661AC4E61230'.

This gives an error:

D:\lab\WiX\XMLEditorheat file PRISMXMLEditor.dll -v  -sfrag -gg -svb6 -out 
foo.xml
Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5210.0
Copyright (C) Microsoft Corporation. All rights reserved.

heat.exe : error HEAT0001 : The path is not of a legal form.

Exception Type: System.ArgumentException

Stack Trace:
   at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
   at System.IO.Path.NormalizePath(String path, Boolean fullCheck)
   at System.IO.Path.GetFullPathInternal(String path)
   at System.IO.Path.GetFullPath(String path)
   at Microsoft.Tools.WindowsInstallerXml.HarvesterCore.ResolveFilePath(String 
fileSource)
   at 
Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateFile(IParentElement
 parentElement, File file)
   at 
Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement
 parentElement, ISchemaElement element)
   at 
Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement
 parentElement, ISchemaElement element)
   at 
Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement
 parentElement, ISchemaElement element)
   at 
Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement
 parentElement, ISchemaElement element)
   at 
Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement
 parentElement, ISchemaElement element)
   at 
Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.MutateElement(IParentElement
 parentElement, ISchemaElement element)
   at 
Microsoft.Tools.WindowsInstallerXml.Extensions.UtilHarvesterMutator.Mutate(Wix 
wix)
   at Microsoft.Tools.WindowsInstallerXml.Mutator.Mutate(Wix wix)
   at Microsoft.Tools.WindowsInstallerXml.Tools.Heat.Run(String[] args)

I ran it with the full path and got this error which looks like it isn't 
reading the path correctly for the 'file' harvesting type argument.  It's 
doubling the name of the last directory in the path 
(d:\lab\wix\xmleditor\xmleditor\PRISMXMLEditor.dll).

So I typed:   d:\lab\wix\xmleditor\PRISMXMLEditor.dll 
But it reads: d:\lab\wix\xmleditor\xmleditor\PRISMXMLEditor.dll 

So that could be hint in as to why the 'file' harvesting type doesn't work, but 
the 'dir' does.  Let me know if there's

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

2009-04-01 Thread Roy Abou Assaly 


I have just tried the latest version 3.0.5120.0 and the programmable
attribute on is set for your dll on the ClassId e.g.

Class Id={5A5DBDF3-10F1-43D1-AA51-CDE7EDFA0321}
Description=PRISMXMLEditor.XMLChunk Version=12.3 Programmable=yes

If you are not already you may also want to try the -svb6 option with
Heat as that will remove the VB6 runtime properties that are not
required (see help file).

Neil


Hi Neil and Roger,

I just ran heat 3.0.5120.0 and got this error:

D:\lab\WiX\XMLEditorheat file PRISMXMLEditor.dll -sfrag -gg -vb6 -out 
result.xml
Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5120.0
Copyright (C) Microsoft Corporation. All rights reserved.

heat.exe : error HEAT0001 : Item has already been added. Key in dictionary: 
'Interface\{0B7F3153-C8E7-4E6D-AEBE-B6D61D78B9A3}\ProxyStubClsid/'  Key being 
added: 'Interface\{0B7F3153-C8E7-4E6
D-AEBE-B6D61D78B9A3}\ProxyStubClsid/'

Exception Type: System.ArgumentException

Stack Trace:
   at System.Collections.SortedList.Add(Object key, Object value)
   at 
Microsoft.Tools.WindowsInstallerXml.Extensions.UtilFinalizeHarvesterMutator.MutateComponents()
   at 
Microsoft.Tools.WindowsInstallerXml.Extensions.UtilFinalizeHarvesterMutator.Mutate(Wix
 wix)
   at Microsoft.Tools.WindowsInstallerXml.Mutator.Mutate(Wix wix)
   at Microsoft.Tools.WindowsInstallerXml.Tools.Heat.Run(String[] args)

Then I ran 3.0.4923.0

D:\lab\WiX\XMLEditorheat file PRISMXMLEditor.dll -sfrag -gg -vb6 -out 
result.xml
Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.4923.0
Copyright (C) Microsoft Corporation. All rights reserved.

And yes, you're right.  Programmable is set as an attribute of Class rather 
than being created in RegistryValue.  I'm going to assume that those 2 are the 
equivalent?  Can you confirm this?  If that is true, I will stick with 
3.0.4923.0 since it works and I have tested the builds with this version.  
That's basically where I got confused.  I saw that I was missing RegistryValue 
elements and figured that certain keys were being missing.

Do you still want me to open a bug Roger?  Although, this time it would be for 
another Reason.  Also, how did it manage to run heat 3.0.5120.0 on your machine 
Neil?  I hope it's not the dreaded It runs on my machine bug :)

Thanks guys
-- 
View this message in context: 
http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2569042.html
Sent from the wix-users mailing list archive at Nabble.com.


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

2009-04-01 Thread Neil Sleightholm 
I just tried this again and didn't see an error, has the dll changed from the 
one you sent me?
 
Neil
 
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com mailto:n...@x2systems.com 
 



From: Roy Abou Assaly [mailto:royass...@gmail.com]
Sent: Wed 01/04/2009 14:39
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat missing some RegistryValue elements 
(Programmable) from VB6 code?





I have just tried the latest version 3.0.5120.0 and the programmable
attribute on is set for your dll on the ClassId e.g.

Class Id={5A5DBDF3-10F1-43D1-AA51-CDE7EDFA0321}
Description=PRISMXMLEditor.XMLChunk Version=12.3 Programmable=yes

If you are not already you may also want to try the -svb6 option with
Heat as that will remove the VB6 runtime properties that are not
required (see help file).

Neil


Hi Neil and Roger,

I just ran heat 3.0.5120.0 and got this error:

D:\lab\WiX\XMLEditorheat file PRISMXMLEditor.dll -sfrag -gg -vb6 -out 
result.xml
Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5120.0
Copyright (C) Microsoft Corporation. All rights reserved.

heat.exe : error HEAT0001 : Item has already been added. Key in dictionary: 
'Interface\{0B7F3153-C8E7-4E6D-AEBE-B6D61D78B9A3}\ProxyStubClsid/'  Key being 
added: 'Interface\{0B7F3153-C8E7-4E6
D-AEBE-B6D61D78B9A3}\ProxyStubClsid/'

Exception Type: System.ArgumentException

Stack Trace:
   at System.Collections.SortedList.Add(Object key, Object value)
   at 
Microsoft.Tools.WindowsInstallerXml.Extensions.UtilFinalizeHarvesterMutator.MutateComponents()
   at 
Microsoft.Tools.WindowsInstallerXml.Extensions.UtilFinalizeHarvesterMutator.Mutate(Wix
 wix)
   at Microsoft.Tools.WindowsInstallerXml.Mutator.Mutate(Wix wix)
   at Microsoft.Tools.WindowsInstallerXml.Tools.Heat.Run(String[] args)

Then I ran 3.0.4923.0

D:\lab\WiX\XMLEditorheat file PRISMXMLEditor.dll -sfrag -gg -vb6 -out 
result.xml
Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.4923.0
Copyright (C) Microsoft Corporation. All rights reserved.

And yes, you're right.  Programmable is set as an attribute of Class rather 
than being created in RegistryValue.  I'm going to assume that those 2 are the 
equivalent?  Can you confirm this?  If that is true, I will stick with 
3.0.4923.0 since it works and I have tested the builds with this version.  
That's basically where I got confused.  I saw that I was missing RegistryValue 
elements and figured that certain keys were being missing.

Do you still want me to open a bug Roger?  Although, this time it would be for 
another Reason.  Also, how did it manage to run heat 3.0.5120.0 on your machine 
Neil?  I hope it's not the dreaded It runs on my machine bug :)

Thanks guys
--
View this message in context: 
http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2569042.html
Sent from the wix-users mailing list archive at Nabble.com.


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

2009-04-01 Thread Roy Abou Assaly 

Hi,
No, I was using version 11.34.  The same one attached in the email.  I just
redownloaded the DLL I had attached to you and ran it in 3.0.5120.0...still
the same exception.  Strange.

On Wed, Apr 1, 2009 at 3:36 PM, Neil Sleightholm (via Nabble) 
ml-user+58265-122838...@n2.nabble.comml-user%2b58265-122838...@n2.nabble.com
 wrote:

 I just tried this again and didn't see an error, has the dll changed from
 the one you sent me?

 Neil

 Neil Sleightholm
 X2 Systems Limited
 n...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=0mailto:
 n...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=1



 

 From: Roy Abou Assaly 
 [mailto:royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=2]

 Sent: Wed 01/04/2009 14:39
 To: 
 wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=3
 Subject: Re: [WiX-users] Heat missing some RegistryValue elements
 (Programmable) from VB6 code?





 I have just tried the latest version 3.0.5120.0 and the programmable
 attribute on is set for your dll on the ClassId e.g.

 Class Id={5A5DBDF3-10F1-43D1-AA51-CDE7EDFA0321}
 Description=PRISMXMLEditor.XMLChunk Version=12.3 Programmable=yes

 If you are not already you may also want to try the -svb6 option with
 Heat as that will remove the VB6 runtime properties that are not
 required (see help file).

 Neil


 Hi Neil and Roger,

 I just ran heat 3.0.5120.0 and got this error:

 D:\lab\WiX\XMLEditorheat file PRISMXMLEditor.dll -sfrag -gg -vb6 -out
 result.xml
 Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5120.0
 Copyright (C) Microsoft Corporation. All rights reserved.

 heat.exe : error HEAT0001 : Item has already been added. Key in dictionary:
 'Interface\{0B7F3153-C8E7-4E6D-AEBE-B6D61D78B9A3}\ProxyStubClsid/'  Key
 being added: 'Interface\{0B7F3153-C8E7-4E6
 D-AEBE-B6D61D78B9A3}\ProxyStubClsid/'

 Exception Type: System.ArgumentException

 Stack Trace:
at System.Collections.SortedList.Add(Object key, Object value)
at
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilFinalizeHarvesterMutator.MutateComponents()

at
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilFinalizeHarvesterMutator.Mutate(Wix
 wix)
at Microsoft.Tools.WindowsInstallerXml.Mutator.Mutate(Wix wix)
at Microsoft.Tools.WindowsInstallerXml.Tools.Heat.Run(String[] args)

 Then I ran 3.0.4923.0

 D:\lab\WiX\XMLEditorheat file PRISMXMLEditor.dll -sfrag -gg -vb6 -out
 result.xml
 Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.4923.0
 Copyright (C) Microsoft Corporation. All rights reserved.

 And yes, you're right.  Programmable is set as an attribute of Class rather
 than being created in RegistryValue.  I'm going to assume that those 2 are
 the equivalent?  Can you confirm this?  If that is true, I will stick with
 3.0.4923.0 since it works and I have tested the builds with this version.
  That's basically where I got confused.  I saw that I was missing
 RegistryValue elements and figured that certain keys were being missing.

 Do you still want me to open a bug Roger?  Although, this time it would be
 for another Reason.  Also, how did it manage to run heat 3.0.5120.0 on your
 machine Neil?  I hope it's not the dreaded It runs on my machine bug :)

 Thanks guys
 --
 View this message in context:
 http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2569042.html
 Sent from the wix-users mailing list archive at Nabble.com.


 --

 ___
 WiX-users mailing list
 wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=4
 https://lists.sourceforge.net/lists/listinfo/wix-users



 --


 ___
 WiX-users mailing list
 wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=5
 https://lists.sourceforge.net/lists/listinfo/wix-users


 --
  View message @
 http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2571127.html
 To unsubscribe from Heat missing some RegistryValue elements (Programmable)
 from VB6 code?, click here (link removed) .




-- 
View this message in context: 
http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2572340.html
Sent from the wix-users mailing list archive at Nabble.com.
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

2009-04-01 Thread Brian Rogers 
Hey Roy,

If you are still able to reproduce this please file a bug in heat and upload
the DLL. I would recommend that the DLL ONLY contain required information to
reproduce the issue IF possible.

Thanks,

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


On Wed, Apr 1, 2009 at 5:07 PM, Roy Abou Assaly royass...@gmail.com wrote:


 Hi,
 No, I was using version 11.34.  The same one attached in the email.  I just
 redownloaded the DLL I had attached to you and ran it in 3.0.5120.0...still
 the same exception.  Strange.

 On Wed, Apr 1, 2009 at 3:36 PM, Neil Sleightholm (via Nabble) 
 ml-user+58265-122838...@n2.nabble.comml-user%2b58265-122838...@n2.nabble.com
 ml-user%2b58265-122838...@n2.nabble.comml-user%252b58265-122838...@n2.nabble.com
 
  wrote:

  I just tried this again and didn't see an error, has the dll changed from
  the one you sent me?
 
  Neil
 
  Neil Sleightholm
  X2 Systems Limited
  n...@...
 http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=0
 mailto:
  n...@...
 http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=1
 
 
 
  
 
  From: Roy Abou Assaly [mailto:royass...@...
 http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=2]
 
  Sent: Wed 01/04/2009 14:39
  To: wix-us...@...
 http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=3
   Subject: Re: [WiX-users] Heat missing some RegistryValue elements
  (Programmable) from VB6 code?
 
 
 
 
 
  I have just tried the latest version 3.0.5120.0 and the programmable
  attribute on is set for your dll on the ClassId e.g.
 
  Class Id={5A5DBDF3-10F1-43D1-AA51-CDE7EDFA0321}
  Description=PRISMXMLEditor.XMLChunk Version=12.3 Programmable=yes
 
  If you are not already you may also want to try the -svb6 option with
  Heat as that will remove the VB6 runtime properties that are not
  required (see help file).
 
  Neil
 
 
  Hi Neil and Roger,
 
  I just ran heat 3.0.5120.0 and got this error:
 
  D:\lab\WiX\XMLEditorheat file PRISMXMLEditor.dll -sfrag -gg -vb6 -out
  result.xml
  Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.5120.0
  Copyright (C) Microsoft Corporation. All rights reserved.
 
  heat.exe : error HEAT0001 : Item has already been added. Key in
 dictionary:
  'Interface\{0B7F3153-C8E7-4E6D-AEBE-B6D61D78B9A3}\ProxyStubClsid/'  Key
  being added: 'Interface\{0B7F3153-C8E7-4E6
  D-AEBE-B6D61D78B9A3}\ProxyStubClsid/'
 
  Exception Type: System.ArgumentException
 
  Stack Trace:
 at System.Collections.SortedList.Add(Object key, Object value)
 at
 
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilFinalizeHarvesterMutator.MutateComponents()
 
 at
 
 Microsoft.Tools.WindowsInstallerXml.Extensions.UtilFinalizeHarvesterMutator.Mutate(Wix
  wix)
 at Microsoft.Tools.WindowsInstallerXml.Mutator.Mutate(Wix wix)
 at Microsoft.Tools.WindowsInstallerXml.Tools.Heat.Run(String[] args)
 
  Then I ran 3.0.4923.0
 
  D:\lab\WiX\XMLEditorheat file PRISMXMLEditor.dll -sfrag -gg -vb6 -out
  result.xml
  Microsoft (R) Windows Installer Xml Toolset Harvester version 3.0.4923.0
  Copyright (C) Microsoft Corporation. All rights reserved.
 
  And yes, you're right.  Programmable is set as an attribute of Class
 rather
  than being created in RegistryValue.  I'm going to assume that those 2
 are
  the equivalent?  Can you confirm this?  If that is true, I will stick
 with
  3.0.4923.0 since it works and I have tested the builds with this version.
   That's basically where I got confused.  I saw that I was missing
  RegistryValue elements and figured that certain keys were being missing.
 
  Do you still want me to open a bug Roger?  Although, this time it would
 be
  for another Reason.  Also, how did it manage to run heat 3.0.5120.0 on
 your
  machine Neil?  I hope it's not the dreaded It runs on my machine bug :)
 
  Thanks guys
  --
  View this message in context:
 
 http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2569042.html
  Sent from the wix-users mailing list archive at Nabble.com.
 
 
 
 --
 
  ___
  WiX-users mailing list
  wix-us...@...
 http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=4
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
 
 
 --
 
 
  ___
  WiX-users mailing list
  wix-us...@...
 http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2571127i=5
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
  --
   View message @
 
 http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2571127.html
  To unsubscribe from Heat missing some RegistryValue elements
 (Programmable)
  from VB6 code

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

2009-03-31 Thread Brian Rogers 
Hey Roy,

Can you download the latest build of heat and try again? There were some
bugs in the registry harvesting that got reported and I fixed. I am not sure
that this would directly fix you issues however.

If it does not, I would like you to open a bug on source forge with the
issue, the steps to reproduce and any other information you could provide to
resolve the issue.

Thanks,

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


On Mon, Mar 30, 2009 at 2:09 PM, Roy Abou Assaly royass...@gmail.comwrote:


 Yes I do.  I have sent it as an attachment to your x2systems email address.

 Thanks!

 Roy

 On Mon, Mar 30, 2009 at 4:55 PM, Neil Sleightholm (via Nabble) 
 ml-user+58265-122838...@n2.nabble.comml-user%2b58265-122838...@n2.nabble.com
 ml-user%2b58265-122838...@n2.nabble.comml-user%252b58265-122838...@n2.nabble.com
 
  wrote:

  Do you have a DLL you could share that shows the problem?
 
  Neil
 
  -Original Message-
  From: Roy Abou Assaly [mailto:royass...@...
 http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2559601i=0]
 
  Sent: 30 March 2009 21:02
   To: wix-us...@...
 http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2559601i=1
  Subject: [WiX-users] Heat missing some RegistryValue elements
  (Programmable) from VB6 code?
 
 
  Hi,
 
  I'm running heat (WiX 3.0.4923.0) to harvest some DLLs.  I don't have
  the version that I was using before, but I know it was working before I
  had upgraded sometime in the Fall.
 
  I noticed that Programmable is being ommitted:
 
 RegistryValue Root=HKCR
  Key=CLSID\{5A5DBDF3-10F1-43D1-AA51-CDE7EDFA0321}\Programmable Value=
  Type=string Action=write /
 
  This key existed in our December build, and now, in many more places in
  the wix file for many DLLs, RegistryValue elements who's key is
  Programmable are no longer there.  I believe keys ending with Control
  may also be affected.  Is this related to this ticket?
  http://sourceforge.net/tracker/?func=detailatid=642714aid=1888456grou
  p_id=105970
 
  Thanks,
 
  Roy
 
  --
  View this message in context:
  http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Program
  mable%29-from-VB6-code--tp2559361p2559361.html
  Sent from the wix-users mailing list archive at Nabble.com.
 
 
  
  --
  ___
  WiX-users mailing list
  wix-us...@...
 http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2559601i=2
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
 --
 
  ___
  WiX-users mailing list
  wix-us...@...
 http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2559601i=3
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
  --
   This email is a reply to your post @
 
 http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2559601.html
  You can reply by email or by visting the link above.
 
 

 --
 View this message in context:
 http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2559657.html
  Sent from the wix-users mailing list archive at Nabble.com.

 --
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

2009-03-31 Thread Neil Sleightholm 
I have just tried the latest version 3.0.5120.0 and the programmable
attribute on is set for your dll on the ClassId e.g.

Class Id={5A5DBDF3-10F1-43D1-AA51-CDE7EDFA0321}
Description=PRISMXMLEditor.XMLChunk Version=12.3 Programmable=yes

If you are not already you may also want to try the -svb6 option with
Heat as that will remove the VB6 runtime properties that are not
required (see help file).

Neil

-Original Message-
From: Roy Abou Assaly [mailto:royass...@gmail.com] 
Sent: 30 March 2009 22:10
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat missing some RegistryValue elements
(Programmable) from VB6 code?


Yes I do.  I have sent it as an attachment to your x2systems email
address.

Thanks!

Roy

On Mon, Mar 30, 2009 at 4:55 PM, Neil Sleightholm (via Nabble) 
ml-user+58265-122838...@n2.nabble.comml-user%2b58265-122838...@n2.nabbl
e.com
 wrote:

 Do you have a DLL you could share that shows the problem?

 Neil

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

 Sent: 30 March 2009 21:02
 To:
wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=255
9601i=1
 Subject: [WiX-users] Heat missing some RegistryValue elements
 (Programmable) from VB6 code?


 Hi,

 I'm running heat (WiX 3.0.4923.0) to harvest some DLLs.  I don't have
 the version that I was using before, but I know it was working before
I
 had upgraded sometime in the Fall.

 I noticed that Programmable is being ommitted:

RegistryValue Root=HKCR
 Key=CLSID\{5A5DBDF3-10F1-43D1-AA51-CDE7EDFA0321}\Programmable
Value=
 Type=string Action=write /

 This key existed in our December build, and now, in many more places
in
 the wix file for many DLLs, RegistryValue elements who's key is
 Programmable are no longer there.  I believe keys ending with Control
 may also be affected.  Is this related to this ticket?

http://sourceforge.net/tracker/?func=detailatid=642714aid=1888456grou
 p_id=105970

 Thanks,

 Roy

 --
 View this message in context:

http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Program
 mable%29-from-VB6-code--tp2559361p2559361.html
 Sent from the wix-users mailing list archive at Nabble.com.




 --
 ___
 WiX-users mailing list

wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=255
9601i=2
 https://lists.sourceforge.net/lists/listinfo/wix-users



--

 ___
 WiX-users mailing list

wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=255
9601i=3
 https://lists.sourceforge.net/lists/listinfo/wix-users


 --
  This email is a reply to your post @

http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Program
mable%29-from-VB6-code--tp2559361p2559601.html
 You can reply by email or by visting the link above.



-- 
View this message in context:
http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Program
mable%29-from-VB6-code--tp2559361p2559657.html
Sent from the wix-users mailing list archive at Nabble.com.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

2009-03-30 Thread Roy Abou Assaly 

Hi,

I'm running heat (WiX 3.0.4923.0) to harvest some DLLs.  I don't have the 
version that I was using before, but I know it was working before I had 
upgraded sometime in the Fall.

I noticed that Programmable is being ommitted:

   RegistryValue Root=HKCR 
Key=CLSID\{5A5DBDF3-10F1-43D1-AA51-CDE7EDFA0321}\Programmable Value= 
Type=string Action=write /

This key existed in our December build, and now, in many more places in the wix 
file for many DLLs, RegistryValue elements who's key is Programmable are no 
longer there.  I believe keys ending with Control may also be affected.  Is 
this related to this ticket? 
http://sourceforge.net/tracker/?func=detailatid=642714aid=1888456group_id=105970

Thanks,

Roy

-- 
View this message in context: 
http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2559361.html
Sent from the wix-users mailing list archive at Nabble.com.


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

2009-03-30 Thread Neil Sleightholm 
Do you have a DLL you could share that shows the problem?

Neil

-Original Message-
From: Roy Abou Assaly [mailto:royass...@gmail.com] 
Sent: 30 March 2009 21:02
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Heat missing some RegistryValue elements
(Programmable) from VB6 code?


Hi,

I'm running heat (WiX 3.0.4923.0) to harvest some DLLs.  I don't have
the version that I was using before, but I know it was working before I
had upgraded sometime in the Fall.

I noticed that Programmable is being ommitted:

   RegistryValue Root=HKCR
Key=CLSID\{5A5DBDF3-10F1-43D1-AA51-CDE7EDFA0321}\Programmable Value=
Type=string Action=write /

This key existed in our December build, and now, in many more places in
the wix file for many DLLs, RegistryValue elements who's key is
Programmable are no longer there.  I believe keys ending with Control
may also be affected.  Is this related to this ticket?
http://sourceforge.net/tracker/?func=detailatid=642714aid=1888456grou
p_id=105970

Thanks,

Roy

-- 
View this message in context:
http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Program
mable%29-from-VB6-code--tp2559361p2559361.html
Sent from the wix-users mailing list archive at Nabble.com.



--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Heat missing some RegistryValue elements (Programmable) from VB6 code?

2009-03-30 Thread Roy Abou Assaly 

Yes I do.  I have sent it as an attachment to your x2systems email address.

Thanks!

Roy

On Mon, Mar 30, 2009 at 4:55 PM, Neil Sleightholm (via Nabble) 
ml-user+58265-122838...@n2.nabble.comml-user%2b58265-122838...@n2.nabble.com
 wrote:

 Do you have a DLL you could share that shows the problem?

 Neil

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

 Sent: 30 March 2009 21:02
 To: 
 wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2559601i=1
 Subject: [WiX-users] Heat missing some RegistryValue elements
 (Programmable) from VB6 code?


 Hi,

 I'm running heat (WiX 3.0.4923.0) to harvest some DLLs.  I don't have
 the version that I was using before, but I know it was working before I
 had upgraded sometime in the Fall.

 I noticed that Programmable is being ommitted:

RegistryValue Root=HKCR
 Key=CLSID\{5A5DBDF3-10F1-43D1-AA51-CDE7EDFA0321}\Programmable Value=
 Type=string Action=write /

 This key existed in our December build, and now, in many more places in
 the wix file for many DLLs, RegistryValue elements who's key is
 Programmable are no longer there.  I believe keys ending with Control
 may also be affected.  Is this related to this ticket?
 http://sourceforge.net/tracker/?func=detailatid=642714aid=1888456grou
 p_id=105970

 Thanks,

 Roy

 --
 View this message in context:
 http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Program
 mable%29-from-VB6-code--tp2559361p2559361.html
 Sent from the wix-users mailing list archive at Nabble.com.


 
 --
 ___
 WiX-users mailing list
 wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2559601i=2
 https://lists.sourceforge.net/lists/listinfo/wix-users

 --

 ___
 WiX-users mailing list
 wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2559601i=3
 https://lists.sourceforge.net/lists/listinfo/wix-users


 --
  This email is a reply to your post @
 http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2559601.html
 You can reply by email or by visting the link above.



-- 
View this message in context: 
http://n2.nabble.com/Heat-missing-some-RegistryValue-elements-%28Programmable%29-from-VB6-code--tp2559361p2559657.html
Sent from the wix-users mailing list archive at Nabble.com.
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users