Re: [WiX-users] Registring CDO.dll - Heat ouput same as before, but Light now giving error

2009-04-22 Thread Roy Abou Assaly

Thanks for the tips guys.  We had 2 products using this.  One works fine with
the redistributable, but the other didn't like it.  So I'm going to chain
the redistributable package for the product that liked it, and we'll just
hold off for the other, until a code change.  We got an error:

Marshaler restriction: Excessively long string.

I will leave to the developers to update accordingly and then our plan is to
use the redistributable.

Thanks!

Roy


Roy Abou Assaly wrote:
 
 Hi Brian,
 I found this website http://www.cdolive.com/cdo7.htm which lead me to this
 MS Collaboration Data Objects, version 1.2.1 (6.5.8067.0) download link:
 http://www.microsoft.com/downloads/details.aspx?familyid=2714320d-c997-4de1-986f-24f081725d36displaylang=en
 
 I'm going to talk to the developer and see if 6.5.8067.0 is compatible
 with
 his application which is using 6.5.7940.0.  If there's no problems, I may
 just go with the MS re-distributable.  I will go that route before I go
 and
 create any unnecessary tickets.  Will get back to with the result.
 
 Thanks for the tip,
 
 Roy
 
 On Mon, Apr 20, 2009 at 4:52 PM, Brian Rogers (via Nabble) 
 ml-user+58646-1457241...@n2.nabble.comml-user%2b58646-1457241...@n2.nabble.com
 wrote:
 
 Roy,

 It might be worth you opening a bug. However, you should not be
 installing
 CDO on your own. There could likely be other pieces that need to be
 installed that are not harvested from the DLL itself. This would
 invalidate

 the installation of CDO on the system and could cause large problems. You
 should look for a redistributable and chain that into your installation.

 The message you are getting in light is saying that the output of the
 harvest is basically not valid which is possible as COM is highly
 customizable. Heat does not take into account all possible variations
 because of those issues.

 Thanks,

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


 On Mon, Apr 20, 2009 at 12:41 PM, Roy Abou Assaly
 royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2666208i=0wrote:


 
  Hi,
 
  I'm in the process of migrating more WiX files to the latest version of
  WiX.
  I'm using 3.0.5217 and found this error that wasn't occurring in an
 older

  version of WiX:
 
  error LGHT0130 : The primary key 'regFB26914512AFF203D5986383999BD192'
 is

  duplicated in table 'Registry'.  Please remove one of the entries or
 rename
  a part of the primary key to avoid the collision.
 
  The DLL in question is actually CDO.dll 6.5.7940.0.  I generated the
 WiX
  for
  it using heat many versions ago (6 months or so).  I regenerated again
  using
  heat 3.0.5217 and it produced the same output.  However, Light 3.0.5217
 is
  throwing the error above.  Light never gave this error before.
 
  If I comment out:
 
   ProgId Id=ActMsg.Session Description=CDO Session Object /
 
  Light has no problems, but after generating the MSI, I ran Orca on the
 MSI,
  and I got:
 
  ICE33:  Warning Reg key regFB26914512AFF203D5986383999BD192 is used in
 an

  unsupported way.  CLSID - ProdId associations should be registered via
 the
  Class and ProdId tables.  This entry may overwrite a value created
 through
  those tables.
 
  Should I create a ticket in sourceforge and attach CDO.dll?
 
  Here's the WiX snippet:
 
 !-- CDO.DLL --
 Component Id=CDO.DLL
  Guid=F1A0C26F-B1CC-4B8D-93C5-EF276E24C3FD SharedDllRefCount=yes
   File Id=CDO.DLL Name=CDO.DLL KeyPath=yes
  Source=$(var.EXTERNAL_DLL)\CDO.DLL
 TypeLib
 Id={3FA7DEA7-6438-101B-ACC1-00AA00423326}
  Description=Microsoft CDO 1.21 Library Language=0 MajorVersion=1
  MinorVersion=21
   Class
 Id={3FA7DEB3-6438-101B-ACC1-00AA00423326}
  Context=InprocServer32 Description=CDO Session Object
  ThreadingModel=both
ProgId Id=ActMsg.Session
 Description=CDO
  Session
  Object /
 ProgId Id=MAPI.Session.1 Description=CDO
  1.21
  Session Object
   ProgId Id=MAPI.Session Description=CDO
  Session
  Object /
 /ProgId
   /Class
 /TypeLib
   /File
 /Component
  --
  View this message in context:
 
 http://n2.nabble.com/Registring-CDO.dll---Heat-ouput-same-as-before%2C-but-Light-now-giving-error-tp2665723p2665723.html
  Sent from the wix-users mailing list archive at Nabble.com.
 
 
 
 
 --

  Stay on top of everything new and different, both inside and
  around Java (TM) technology - register by April 22, and save
  $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
  300 plus technical and hands-on sessions. Register today.
  Use priority code J9JMT32. http://p.sf.net/sfu/p
  

[WiX-users] Registring CDO.dll - Heat ouput same as before, but Light now giving error

2009-04-20 Thread Roy Abou Assaly

Hi,

I'm in the process of migrating more WiX files to the latest version of WiX. 
I'm using 3.0.5217 and found this error that wasn't occurring in an older
version of WiX:

error LGHT0130 : The primary key 'regFB26914512AFF203D5986383999BD192' is
duplicated in table 'Registry'.  Please remove one of the entries or rename
a part of the primary key to avoid the collision.

The DLL in question is actually CDO.dll 6.5.7940.0.  I generated the WiX for
it using heat many versions ago (6 months or so).  I regenerated again using
heat 3.0.5217 and it produced the same output.  However, Light 3.0.5217 is
throwing the error above.  Light never gave this error before.

If I comment out:

  ProgId Id=ActMsg.Session Description=CDO Session Object /

Light has no problems, but after generating the MSI, I ran Orca on the MSI,
and I got:

ICE33:  Warning Reg key regFB26914512AFF203D5986383999BD192 is used in an
unsupported way.  CLSID - ProdId associations should be registered via the
Class and ProdId tables.  This entry may overwrite a value created through
those tables.

Should I create a ticket in sourceforge and attach CDO.dll?

Here's the WiX snippet:

!-- CDO.DLL --
Component Id=CDO.DLL
Guid=F1A0C26F-B1CC-4B8D-93C5-EF276E24C3FD SharedDllRefCount=yes
  File Id=CDO.DLL Name=CDO.DLL KeyPath=yes
Source=$(var.EXTERNAL_DLL)\CDO.DLL
TypeLib Id={3FA7DEA7-6438-101B-ACC1-00AA00423326}
Description=Microsoft CDO 1.21 Library Language=0 MajorVersion=1
MinorVersion=21
  Class Id={3FA7DEB3-6438-101B-ACC1-00AA00423326}
Context=InprocServer32 Description=CDO Session Object
ThreadingModel=both
   ProgId Id=ActMsg.Session Description=CDO 
Session
Object /
ProgId Id=MAPI.Session.1 Description=CDO 1.21
Session Object
  ProgId Id=MAPI.Session Description=CDO Session
Object /
/ProgId
  /Class
/TypeLib
  /File
/Component
-- 
View this message in context: 
http://n2.nabble.com/Registring-CDO.dll---Heat-ouput-same-as-before%2C-but-Light-now-giving-error-tp2665723p2665723.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Registring CDO.dll - Heat ouput same as before, but Light now giving error

2009-04-20 Thread Brian Rogers
Roy,

It might be worth you opening a bug. However, you should not be installing
CDO on your own. There could likely be other pieces that need to be
installed that are not harvested from the DLL itself. This would invalidate
the installation of CDO on the system and could cause large problems. You
should look for a redistributable and chain that into your installation.

The message you are getting in light is saying that the output of the
harvest is basically not valid which is possible as COM is highly
customizable. Heat does not take into account all possible variations
because of those issues.

Thanks,

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


On Mon, Apr 20, 2009 at 12:41 PM, Roy Abou Assaly royass...@gmail.comwrote:


 Hi,

 I'm in the process of migrating more WiX files to the latest version of
 WiX.
 I'm using 3.0.5217 and found this error that wasn't occurring in an older
 version of WiX:

 error LGHT0130 : The primary key 'regFB26914512AFF203D5986383999BD192' is
 duplicated in table 'Registry'.  Please remove one of the entries or rename
 a part of the primary key to avoid the collision.

 The DLL in question is actually CDO.dll 6.5.7940.0.  I generated the WiX
 for
 it using heat many versions ago (6 months or so).  I regenerated again
 using
 heat 3.0.5217 and it produced the same output.  However, Light 3.0.5217 is
 throwing the error above.  Light never gave this error before.

 If I comment out:

  ProgId Id=ActMsg.Session Description=CDO Session Object /

 Light has no problems, but after generating the MSI, I ran Orca on the MSI,
 and I got:

 ICE33:  Warning Reg key regFB26914512AFF203D5986383999BD192 is used in an
 unsupported way.  CLSID - ProdId associations should be registered via the
 Class and ProdId tables.  This entry may overwrite a value created through
 those tables.

 Should I create a ticket in sourceforge and attach CDO.dll?

 Here's the WiX snippet:

!-- CDO.DLL --
Component Id=CDO.DLL
 Guid=F1A0C26F-B1CC-4B8D-93C5-EF276E24C3FD SharedDllRefCount=yes
  File Id=CDO.DLL Name=CDO.DLL KeyPath=yes
 Source=$(var.EXTERNAL_DLL)\CDO.DLL
TypeLib Id={3FA7DEA7-6438-101B-ACC1-00AA00423326}
 Description=Microsoft CDO 1.21 Library Language=0 MajorVersion=1
 MinorVersion=21
  Class Id={3FA7DEB3-6438-101B-ACC1-00AA00423326}
 Context=InprocServer32 Description=CDO Session Object
 ThreadingModel=both
   ProgId Id=ActMsg.Session Description=CDO
 Session
 Object /
ProgId Id=MAPI.Session.1 Description=CDO
 1.21
 Session Object
  ProgId Id=MAPI.Session Description=CDO
 Session
 Object /
/ProgId
  /Class
/TypeLib
  /File
/Component
 --
 View this message in context:
 http://n2.nabble.com/Registring-CDO.dll---Heat-ouput-same-as-before%2C-but-Light-now-giving-error-tp2665723p2665723.html
 Sent from the wix-users mailing list archive at Nabble.com.



 --
 Stay on top of everything new and different, both inside and
 around Java (TM) technology - register by April 22, and save
 $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
 300 plus technical and hands-on sessions. Register today.
 Use priority code J9JMT32. http://p.sf.net/sfu/p
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Registring CDO.dll - Heat ouput same as before, but Light now giving error

2009-04-20 Thread Wilson, Phil
I was about to say the same thing.  There is a redist, ExchangeCDO.exe, that 
wraps an MSI file:

http://www.microsoft.com/downloads/details.aspx?FamilyID=2714320D-C997-4DE1-986F-24F081725D36displaylang=en
 

containing a CDO.Dll version of 6.5.8067.0. There are other related downloads 
at this kb article: 

http://support.microsoft.com/kb/171440 

Phil Wilson 

-Original Message-
From: Brian Rogers [mailto:rogers.br...@gmail.com] 
Sent: Monday, April 20, 2009 1:48 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Registring CDO.dll - Heat ouput same as before, but 
Light now giving error

Roy,

It might be worth you opening a bug. However, you should not be installing
CDO on your own. There could likely be other pieces that need to be
installed that are not harvested from the DLL itself. This would invalidate
the installation of CDO on the system and could cause large problems. You
should look for a redistributable and chain that into your installation.

The message you are getting in light is saying that the output of the
harvest is basically not valid which is possible as COM is highly
customizable. Heat does not take into account all possible variations
because of those issues.

Thanks,

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


On Mon, Apr 20, 2009 at 12:41 PM, Roy Abou Assaly royass...@gmail.comwrote:


 Hi,

 I'm in the process of migrating more WiX files to the latest version of
 WiX.
 I'm using 3.0.5217 and found this error that wasn't occurring in an older
 version of WiX:

 error LGHT0130 : The primary key 'regFB26914512AFF203D5986383999BD192' is
 duplicated in table 'Registry'.  Please remove one of the entries or rename
 a part of the primary key to avoid the collision.

 The DLL in question is actually CDO.dll 6.5.7940.0.  I generated the WiX
 for
 it using heat many versions ago (6 months or so).  I regenerated again
 using
 heat 3.0.5217 and it produced the same output.  However, Light 3.0.5217 is
 throwing the error above.  Light never gave this error before.

 If I comment out:

  ProgId Id=ActMsg.Session Description=CDO Session Object /

 Light has no problems, but after generating the MSI, I ran Orca on the MSI,
 and I got:

 ICE33:  Warning Reg key regFB26914512AFF203D5986383999BD192 is used in an
 unsupported way.  CLSID - ProdId associations should be registered via the
 Class and ProdId tables.  This entry may overwrite a value created through
 those tables.

 Should I create a ticket in sourceforge and attach CDO.dll?

 Here's the WiX snippet:

!-- CDO.DLL --
Component Id=CDO.DLL
 Guid=F1A0C26F-B1CC-4B8D-93C5-EF276E24C3FD SharedDllRefCount=yes
  File Id=CDO.DLL Name=CDO.DLL KeyPath=yes
 Source=$(var.EXTERNAL_DLL)\CDO.DLL
TypeLib Id={3FA7DEA7-6438-101B-ACC1-00AA00423326}
 Description=Microsoft CDO 1.21 Library Language=0 MajorVersion=1
 MinorVersion=21
  Class Id={3FA7DEB3-6438-101B-ACC1-00AA00423326}
 Context=InprocServer32 Description=CDO Session Object
 ThreadingModel=both
   ProgId Id=ActMsg.Session Description=CDO
 Session
 Object /
ProgId Id=MAPI.Session.1 Description=CDO
 1.21
 Session Object
  ProgId Id=MAPI.Session Description=CDO
 Session
 Object /
/ProgId
  /Class
/TypeLib
  /File
/Component
 --
 View this message in context:
 http://n2.nabble.com/Registring-CDO.dll---Heat-ouput-same-as-before%2C-but-Light-now-giving-error-tp2665723p2665723.html
 Sent from the wix-users mailing list archive at Nabble.com.



 --
 Stay on top of everything new and different, both inside and
 around Java (TM) technology - register by April 22, and save
 $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
 300 plus technical and hands-on sessions. Register today.
 Use priority code J9JMT32. http://p.sf.net/sfu/p
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Stay on top of everything new

Re: [WiX-users] Registring CDO.dll - Heat ouput same as before, but Light now giving error

2009-04-20 Thread Roy Abou Assaly

Hi Brian,
I found this website http://www.cdolive.com/cdo7.htm which lead me to this
MS Collaboration Data Objects, version 1.2.1 (6.5.8067.0) download link:
http://www.microsoft.com/downloads/details.aspx?familyid=2714320d-c997-4de1-986f-24f081725d36displaylang=en

I'm going to talk to the developer and see if 6.5.8067.0 is compatible with
his application which is using 6.5.7940.0.  If there's no problems, I may
just go with the MS re-distributable.  I will go that route before I go and
create any unnecessary tickets.  Will get back to with the result.

Thanks for the tip,

Roy

On Mon, Apr 20, 2009 at 4:52 PM, Brian Rogers (via Nabble) 
ml-user+58646-1457241...@n2.nabble.comml-user%2b58646-1457241...@n2.nabble.com
 wrote:

 Roy,

 It might be worth you opening a bug. However, you should not be installing
 CDO on your own. There could likely be other pieces that need to be
 installed that are not harvested from the DLL itself. This would invalidate

 the installation of CDO on the system and could cause large problems. You
 should look for a redistributable and chain that into your installation.

 The message you are getting in light is saying that the output of the
 harvest is basically not valid which is possible as COM is highly
 customizable. Heat does not take into account all possible variations
 because of those issues.

 Thanks,

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


 On Mon, Apr 20, 2009 at 12:41 PM, Roy Abou Assaly 
 royass...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2666208i=0wrote:


 
  Hi,
 
  I'm in the process of migrating more WiX files to the latest version of
  WiX.
  I'm using 3.0.5217 and found this error that wasn't occurring in an older

  version of WiX:
 
  error LGHT0130 : The primary key 'regFB26914512AFF203D5986383999BD192' is

  duplicated in table 'Registry'.  Please remove one of the entries or
 rename
  a part of the primary key to avoid the collision.
 
  The DLL in question is actually CDO.dll 6.5.7940.0.  I generated the WiX
  for
  it using heat many versions ago (6 months or so).  I regenerated again
  using
  heat 3.0.5217 and it produced the same output.  However, Light 3.0.5217
 is
  throwing the error above.  Light never gave this error before.
 
  If I comment out:
 
   ProgId Id=ActMsg.Session Description=CDO Session Object /
 
  Light has no problems, but after generating the MSI, I ran Orca on the
 MSI,
  and I got:
 
  ICE33:  Warning Reg key regFB26914512AFF203D5986383999BD192 is used in an

  unsupported way.  CLSID - ProdId associations should be registered via
 the
  Class and ProdId tables.  This entry may overwrite a value created
 through
  those tables.
 
  Should I create a ticket in sourceforge and attach CDO.dll?
 
  Here's the WiX snippet:
 
 !-- CDO.DLL --
 Component Id=CDO.DLL
  Guid=F1A0C26F-B1CC-4B8D-93C5-EF276E24C3FD SharedDllRefCount=yes
   File Id=CDO.DLL Name=CDO.DLL KeyPath=yes
  Source=$(var.EXTERNAL_DLL)\CDO.DLL
 TypeLib
 Id={3FA7DEA7-6438-101B-ACC1-00AA00423326}
  Description=Microsoft CDO 1.21 Library Language=0 MajorVersion=1
  MinorVersion=21
   Class
 Id={3FA7DEB3-6438-101B-ACC1-00AA00423326}
  Context=InprocServer32 Description=CDO Session Object
  ThreadingModel=both
ProgId Id=ActMsg.Session
 Description=CDO
  Session
  Object /
 ProgId Id=MAPI.Session.1 Description=CDO
  1.21
  Session Object
   ProgId Id=MAPI.Session Description=CDO
  Session
  Object /
 /ProgId
   /Class
 /TypeLib
   /File
 /Component
  --
  View this message in context:
 
 http://n2.nabble.com/Registring-CDO.dll---Heat-ouput-same-as-before%2C-but-Light-now-giving-error-tp2665723p2665723.html
  Sent from the wix-users mailing list archive at Nabble.com.
 
 
 
 
 --

  Stay on top of everything new and different, both inside and
  around Java (TM) technology - register by April 22, and save
  $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
  300 plus technical and hands-on sessions. Register today.
  Use priority code J9JMT32. http://p.sf.net/sfu/p
  ___
  WiX-users mailing list
  wix-us...@...http://n2.nabble.com/user/SendEmail.jtp?type=nodenode=2666208i=1
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 --

 Stay on top of everything new and different, both inside and
 around Java (TM) technology - register by April 22, and save
 $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
 300 plus technical and hands-on sessions. Register today.
 Use