[WiX-users] Registering VB6 OCX with Wix 3

2009-06-25 Thread MacDiarmid, James D 

Hi All,

I ran heat on one of my OCX components using the -scom and -sfrag
switches. In the following output, on the 4th line from the top and the
4th line from the bottom ther is a long alphanumeric string and I'm not
sure what to replace the values with.  Any thoughts?

Component Id=NTSVC
Guid={4F850F61-E0CB-41CA-BFC3-EC5234D1D003}
  File Id=ntsvc.ocx KeyPath=yes
Source=SourceDir\binaries\ntsvc.ocx Vital=yes/
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\Control Value=
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\InprocServer32
Value=[!filCF703A9BAE43C19E5A2520BB35E21977] Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\MiscStatus\1
Value=199824 Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\MiscStatus Value=0
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\ProgID
Value=NTService.Control.1 Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\ToolboxBitmap32
Value=[!filCF703A9BAE43C19E5A2520BB35E21977], 1 Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Value={E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\Version Value=1.0
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C} Value=NT Service
Control Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid32
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Value={E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Name=Version Value=1.0 Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C} Value=_DNtSvc
Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid32
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Value={E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Name=Version Value=1.0 Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}
Value=_DNtSvcEvents Type=string Action=write /
  RegistryValue Root=HKCR Key=NTService.Control.1\CLSID
Value={E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR Key=NTService.Control.1
Value=NT Service Control Type=string Action=write /
  RegistryValue Root=HKCR
Key=TypeLib\{E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C}\1.0\0\win32
Value=[!filCF703A9BAE43C19E5A2520BB35E21977] Type=string
Action=write /
  RegistryValue Root=HKCR
Key=TypeLib\{E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C}\1.0\FLAGS Value=2
Type=string Action=write /
  RegistryValue Root=HKCR
Key=TypeLib\{E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C}\1.0\HELPDIR
Value=D:\Projects\NFTS\Src\apps\nfts\binaries Type=string
Action=write /
  RegistryValue Root=HKCR
Key=TypeLib\{E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C}\1.0
Value=Microsoft NT Service Control Type=string Action=write /
/Component




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

Re: [WiX-users] Registering VB6 OCX with Wix 3

2009-06-25 Thread Pally Sandher 
It's a file identifier. Run heat with the -suid option  it will make
more sense (why this isn't default is beyond me). The ! means it will be
translated to a short path name during the install. See
http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx 

You probably want to run heat with -svb6 too btw.

Also in future snip your code down to the relevant parts as saying on
the 4th line from the top when each line of your code is being split
across multiple lines by the list bot doesn't help people trying to help
you (it's actually the 9th line as you can see below).

Palbinder Sandher 
Software Deployment  IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
 
 

-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com] 
Sent: 25 June 2009 15:58
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Registering VB6 OCX with Wix 3


Hi All,

I ran heat on one of my OCX components using the -scom and -sfrag
switches. In the following output, on the 4th line from the top and the
4th line from the bottom ther is a long alphanumeric string and I'm not
sure what to replace the values with.  Any thoughts?

Component Id=NTSVC
Guid={4F850F61-E0CB-41CA-BFC3-EC5234D1D003}
  File Id=ntsvc.ocx KeyPath=yes
Source=SourceDir\binaries\ntsvc.ocx Vital=yes/
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\Control Value=
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\InprocServer32
Value=[!filCF703A9BAE43C19E5A2520BB35E21977] Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\MiscStatus\1
Value=199824 Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\MiscStatus Value=0
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\ProgID
Value=NTService.Control.1 Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\ToolboxBitmap32
Value=[!filCF703A9BAE43C19E5A2520BB35E21977], 1 Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Value={E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\Version Value=1.0
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C} Value=NT Service
Control Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid32
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Value={E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Name=Version Value=1.0 Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C} Value=_DNtSvc
Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid32
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Value={E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Name=Version Value=1.0 Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}
Value=_DNtSvcEvents Type=string Action=write /
  RegistryValue Root=HKCR Key=NTService.Control.1\CLSID
Value={E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR Key=NTService.Control.1
Value=NT Service Control Type=string Action=write /
  RegistryValue Root=HKCR
Key=TypeLib\{E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C}\1.0\0\win32
Value=[!filCF703A9BAE43C19E5A2520BB35E21977] Type=string

Re: [WiX-users] Registering VB6 OCX with Wix 3

2009-06-25 Thread MacDiarmid, James D 

Thanks Pally.   Just out of curiousity, why would I need to run it with
the -svb6 option?  Wouldn't that trim out the registry settings for the
VB6 Runtime files? 

Thanks for the recommendation on snipping things down.  Sorry about
about that.  :)

Jim

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Thursday, June 25, 2009 11:14 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registering VB6 OCX with Wix 3

It's a file identifier. Run heat with the -suid option  it will make
more sense (why this isn't default is beyond me). The ! means it will be
translated to a short path name during the install. See
http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx 

You probably want to run heat with -svb6 too btw.

Also in future snip your code down to the relevant parts as saying on
the 4th line from the top when each line of your code is being split
across multiple lines by the list bot doesn't help people trying to help
you (it's actually the 9th line as you can see below).

Palbinder Sandher
Software Deployment  IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501 

http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP Email Disclaimer
 
 

-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com] 
Sent: 25 June 2009 15:58
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Registering VB6 OCX with Wix 3


Hi All,

I ran heat on one of my OCX components using the -scom and -sfrag
switches. In the following output, on the 4th line from the top and the
4th line from the bottom ther is a long alphanumeric string and I'm not
sure what to replace the values with.  Any thoughts?

Component Id=NTSVC
Guid={4F850F61-E0CB-41CA-BFC3-EC5234D1D003}
  File Id=ntsvc.ocx KeyPath=yes
Source=SourceDir\binaries\ntsvc.ocx Vital=yes/
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\Control Value=
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\InprocServer32
Value=[!filCF703A9BAE43C19E5A2520BB35E21977] Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\MiscStatus\1
Value=199824 Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\MiscStatus Value=0
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\ProgID
Value=NTService.Control.1 Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\ToolboxBitmap32
Value=[!filCF703A9BAE43C19E5A2520BB35E21977], 1 Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Value={E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\Version Value=1.0
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C} Value=NT Service
Control Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid32
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Value={E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Name=Version Value=1.0 Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C} Value=_DNtSvc
Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid32
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Value={E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Name=Version Value=1.0 Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2

Re: [WiX-users] Registering VB6 OCX with Wix 3

2009-06-25 Thread Neil Sleightholm 
The -vb6 option stops heat generating registry entries that shouldn't be
removed when the component is uninstalled - vb6 components break the
proper COM rules by registering things that are not part of the
component being registered.

Neil

-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com] 
Sent: 25 June 2009 16:37
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registering VB6 OCX with Wix 3


Thanks Pally.   Just out of curiousity, why would I need to run it with
the -svb6 option?  Wouldn't that trim out the registry settings for the
VB6 Runtime files? 

Thanks for the recommendation on snipping things down.  Sorry about
about that.  :)

Jim

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Thursday, June 25, 2009 11:14 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registering VB6 OCX with Wix 3

It's a file identifier. Run heat with the -suid option  it will make
more sense (why this isn't default is beyond me). The ! means it will be
translated to a short path name during the install. See
http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx 

You probably want to run heat with -svb6 too btw.

Also in future snip your code down to the relevant parts as saying on
the 4th line from the top when each line of your code is being split
across multiple lines by the list bot doesn't help people trying to help
you (it's actually the 9th line as you can see below).

Palbinder Sandher
Software Deployment  IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501 

http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP Email Disclaimer
 
 

-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com] 
Sent: 25 June 2009 15:58
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Registering VB6 OCX with Wix 3


Hi All,

I ran heat on one of my OCX components using the -scom and -sfrag
switches. In the following output, on the 4th line from the top and the
4th line from the bottom ther is a long alphanumeric string and I'm not
sure what to replace the values with.  Any thoughts?

Component Id=NTSVC
Guid={4F850F61-E0CB-41CA-BFC3-EC5234D1D003}
  File Id=ntsvc.ocx KeyPath=yes
Source=SourceDir\binaries\ntsvc.ocx Vital=yes/
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\Control Value=
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\InprocServer32
Value=[!filCF703A9BAE43C19E5A2520BB35E21977] Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\MiscStatus\1
Value=199824 Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\MiscStatus Value=0
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\ProgID
Value=NTService.Control.1 Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\ToolboxBitmap32
Value=[!filCF703A9BAE43C19E5A2520BB35E21977], 1 Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Value={E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\Version Value=1.0
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C} Value=NT Service
Control Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid32
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Value={E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Name=Version Value=1.0 Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C} Value=_DNtSvc
Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A2-BA86-11CF-84B1-CBC2DA68BF6C

Re: [WiX-users] Registering VB6 OCX with Wix 3

2009-06-25 Thread MacDiarmid, James D 

Ah!  Very good information!  I did not know that. 

Thank you 

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com] 
Sent: Thursday, June 25, 2009 4:12 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registering VB6 OCX with Wix 3

The -vb6 option stops heat generating registry entries that shouldn't be
removed when the component is uninstalled - vb6 components break the
proper COM rules by registering things that are not part of the
component being registered.

Neil

-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com]
Sent: 25 June 2009 16:37
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registering VB6 OCX with Wix 3


Thanks Pally.   Just out of curiousity, why would I need to run it with
the -svb6 option?  Wouldn't that trim out the registry settings for the
VB6 Runtime files? 

Thanks for the recommendation on snipping things down.  Sorry about
about that.  :)

Jim

-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Thursday, June 25, 2009 11:14 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registering VB6 OCX with Wix 3

It's a file identifier. Run heat with the -suid option  it will make
more sense (why this isn't default is beyond me). The ! means it will be
translated to a short path name during the install. See
http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx 

You probably want to run heat with -svb6 too btw.

Also in future snip your code down to the relevant parts as saying on
the 4th line from the top when each line of your code is being split
across multiple lines by the list bot doesn't help people trying to help
you (it's actually the 9th line as you can see below).

Palbinder Sandher
Software Deployment  IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501 

http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP Email Disclaimer
 
 

-Original Message-
From: MacDiarmid, James D [mailto:james.macdiar...@eds.com] 
Sent: 25 June 2009 15:58
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Registering VB6 OCX with Wix 3


Hi All,

I ran heat on one of my OCX components using the -scom and -sfrag
switches. In the following output, on the 4th line from the top and the
4th line from the bottom ther is a long alphanumeric string and I'm not
sure what to replace the values with.  Any thoughts?

Component Id=NTSVC
Guid={4F850F61-E0CB-41CA-BFC3-EC5234D1D003}
  File Id=ntsvc.ocx KeyPath=yes
Source=SourceDir\binaries\ntsvc.ocx Vital=yes/
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\Control Value=
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\InprocServer32
Value=[!filCF703A9BAE43C19E5A2520BB35E21977] Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\MiscStatus\1
Value=199824 Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\MiscStatus Value=0
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\ProgID
Value=NTService.Control.1 Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\ToolboxBitmap32
Value=[!filCF703A9BAE43C19E5A2520BB35E21977], 1 Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Value={E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C}\Version Value=1.0
Type=string Action=write /
  RegistryValue Root=HKCR
Key=CLSID\{E7BC34A3-BA86-11CF-84B1-CBC2DA68BF6C} Value=NT Service
Control Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\ProxyStubClsid32
Value={00020420---C000-0046} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Value={E7BC34A0-BA86-11CF-84B1-CBC2DA68BF6C} Type=string
Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C}\TypeLib
Name=Version Value=1.0 Type=string Action=write /
  RegistryValue Root=HKCR
Key=Interface\{E7BC34A1-BA86-11CF-84B1-CBC2DA68BF6C} Value=_DNtSvc

Re: [WiX-users] Registering an OCX

2007-09-25 Thread Brad Stanley 
OK, I've tried both methods suggested by John and cannot seem to get  
the control registered on Vista with UAC enabled.  On XP and Vista  
without UAC (a Mac running Vista via Parallels) it registers the  
control and works fine.

Our old InstallerVise installer registers the control just fine in  
Vista with UAC, so I know it can be done.

Is there something else I might be missing?


On Sep 14, 2007, at 12:01 PM, Wilson, Phil wrote:

  and adding to John's comment, if it's a Vista machine where it
 fails then the issue is likely to be UAC. Even an administrator  
 doesn't
 always run with admin privileges, and that applies to impersonated
 custom actions too.
 http://msdn2.microsoft.com/en-us/library/aa372468.aspx
 http://blogs.msdn.com/astebner/archive/2006/09/30/778865.aspx
 http://www.macrovision.com/webdocuments/PDF/is_vista.pdf

 Phil Wilson

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of John  
 Hall
 Sent: Friday, September 14, 2007 9:22 AM
 To: Brad Stanley
 Cc: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Registering an OCX

 Our software package needs to register an Active X Control.
 Currently I do it with the following:

 ---
 Property Id='REGSVR'regsvr32.exe/Property

  CustomAction Id=RegisterOCX Return=asyncNoWait
 Property=REGSVR ExeCommand='/s [INSTALLDIR]MyControl.ocx' /

 Should I be following another method to register the OCX so
 it consistently registers?

 Brad,

 A much better approach is to extract the registry entries that your  
 OCX
 creates and create the registry entries directly from your installer.
 WiX 2 includes a utility 'tallow' [1] and WiX 3 a utility called  
 'heat'
 [2] that will do most of the work for you.

 Regards,
 John

 [1]
 http://blogs.conchango.com/stuartpreston/archive/2005/12/10/2488.aspx
 [2]
 http://installing.blogspot.com/2006/04/heatexe-making-setup- 
 easier.html



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Registering an OCX

2007-09-14 Thread Brad Stanley 
Our software package needs to register an Active X Control.   
Currently I do it with the following:

---
Property Id='REGSVR'regsvr32.exe/Property

 CustomAction Id=RegisterOCX Return=asyncNoWait  
Property=REGSVR ExeCommand='/s [INSTALLDIR]MyControl.ocx' /

 InstallExecuteSequence
   Custom Action=RegisterOCX After=InstallFinalize/
 /InstallExecuteSequence
---

This works fine on Windows XP.  Windows Vista works fine on my  
computer, but on another computer the install completes without  
registering the OCX successfully.  I try to manually register the OCX  
on the user's computer and I get an Error 0x80070005.  From what I've  
read, this indicates a permission problem, even though the user is an  
Administrator.

Should I be following another method to register the OCX so it  
consistently registers?


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Registering an OCX

2007-09-14 Thread John Hall 
 Our software package needs to register an Active X Control.   
 Currently I do it with the following:
 
 ---
 Property Id='REGSVR'regsvr32.exe/Property
 
  CustomAction Id=RegisterOCX Return=asyncNoWait  
 Property=REGSVR ExeCommand='/s [INSTALLDIR]MyControl.ocx' /

 Should I be following another method to register the OCX so 
 it consistently registers?

Brad,

A much better approach is to extract the registry entries that your OCX
creates and create the registry entries directly from your installer.
WiX 2 includes a utility 'tallow' [1] and WiX 3 a utility called 'heat'
[2] that will do most of the work for you.

Regards,
John

[1]
http://blogs.conchango.com/stuartpreston/archive/2005/12/10/2488.aspx
[2]
http://installing.blogspot.com/2006/04/heatexe-making-setup-easier.html

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Registering an OCX

2007-09-14 Thread Wilson, Phil 
 and adding to John's comment, if it's a Vista machine where it
fails then the issue is likely to be UAC. Even an administrator doesn't
always run with admin privileges, and that applies to impersonated
custom actions too.  
http://msdn2.microsoft.com/en-us/library/aa372468.aspx 
http://blogs.msdn.com/astebner/archive/2006/09/30/778865.aspx
http://www.macrovision.com/webdocuments/PDF/is_vista.pdf 

Phil Wilson 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Hall
Sent: Friday, September 14, 2007 9:22 AM
To: Brad Stanley
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Registering an OCX

 Our software package needs to register an Active X Control.   
 Currently I do it with the following:
 
 ---
 Property Id='REGSVR'regsvr32.exe/Property
 
  CustomAction Id=RegisterOCX Return=asyncNoWait  
 Property=REGSVR ExeCommand='/s [INSTALLDIR]MyControl.ocx' /

 Should I be following another method to register the OCX so 
 it consistently registers?

Brad,

A much better approach is to extract the registry entries that your OCX
creates and create the registry entries directly from your installer.
WiX 2 includes a utility 'tallow' [1] and WiX 3 a utility called 'heat'
[2] that will do most of the work for you.

Regards,
John

[1]
http://blogs.conchango.com/stuartpreston/archive/2005/12/10/2488.aspx
[2]
http://installing.blogspot.com/2006/04/heatexe-making-setup-easier.html


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Registering an OCX with Wix v3?

2007-04-02 Thread Chuck 
I'm trying to register an OCX control.

I ran heat.exe and used the output in my wix project but the ocx isn't 
properly registered???

If can manually register the ocx using a command line with regsvr32.exe 
and it registers properly.

Am I missing something or does heat not work with ocx controls.

Thanx
Chuck

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Registering an OCX with Wix v3?

2007-04-02 Thread Mike Dimmick 
Heat attempts to run the DLL's DllRegisterServer function and then work out
what it did. Like most reverse engineering, it's not very reliable, and it's
heavily dependent on the DllRegisterServer code working correctly in the
unusual, artificial environment that Heat creates. This is done both to
filter out everything that's already present in the registry, and to stop
the DLL's changes from being applied to the real registry.

It's far better to work out what registry settings it's going to create and
author the appropriate WiX script yourself. This is obviously more work.

An OCX is simply a DLL with a different extension. There's no real reason
for the changed extension. You can implement ActiveX controls in a DLL file
and OCX files don't necessarily contain any ActiveX controls. The MFC
ActiveX project wizards normally sets the extension to OCX, while ATL
doesn't bother.

-- 
Mike Dimmick

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chuck
Sent: 02 April 2007 19:53
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Registering an OCX with Wix v3?

I'm trying to register an OCX control.

I ran heat.exe and used the output in my wix project but the ocx isn't 
properly registered???

If can manually register the ocx using a command line with regsvr32.exe 
and it registers properly.

Am I missing something or does heat not work with ocx controls.



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Registering an OCX with Wix v3?

2007-04-02 Thread Chris Bardon 
Yeah, I haven't had any luck with Heat either, but the reverse
engineering isn't all that tricky actually.  Grab the trial version of
RegSnap from http://lastbit.com/regsnap/ and try unregistering your
control, taking a snapshot, registering, taking a snapshot, and
comparing the two.  There'll be some junk in there, but it should be
easy to find what you're looking for.  Then, convert to WiX, and you're
done.  

Chris 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Dimmick
Sent: Monday, April 02, 2007 3:27 PM
To: 'Chuck'; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Registering an OCX with Wix v3?

Heat attempts to run the DLL's DllRegisterServer function and then work
out what it did. Like most reverse engineering, it's not very reliable,
and it's heavily dependent on the DllRegisterServer code working
correctly in the unusual, artificial environment that Heat creates. This
is done both to filter out everything that's already present in the
registry, and to stop the DLL's changes from being applied to the real
registry.

It's far better to work out what registry settings it's going to create
and author the appropriate WiX script yourself. This is obviously more
work.

An OCX is simply a DLL with a different extension. There's no real
reason for the changed extension. You can implement ActiveX controls in
a DLL file and OCX files don't necessarily contain any ActiveX controls.
The MFC ActiveX project wizards normally sets the extension to OCX,
while ATL doesn't bother.

--
Mike Dimmick

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chuck
Sent: 02 April 2007 19:53
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Registering an OCX with Wix v3?

I'm trying to register an OCX control.

I ran heat.exe and used the output in my wix project but the ocx isn't
properly registered???

If can manually register the ocx using a command line with regsvr32.exe
and it registers properly.

Am I missing something or does heat not work with ocx controls.




-
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDE
V
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users