Re: [WiX-users] wix 2.0 to 3.0 - COM registration

2007-10-25 Thread Karim MacDonald 


Strele Franz-2 wrote:
> 
> You can use the 'undocumented' "-scom" switch with heat.exe to generate
> only RegistryKey/RegistryValue-entries (instead of Class/ProgId/...).
> 
Many thanks Stele, for both posts: the -scom switch works perfectly & I can
use it guilt-free! I wonder if there's a feature-request for heat.exe to
automatically use -scom for .NET COM libs..? :0)

Karim
-- 
View this message in context: 
http://www.nabble.com/wix-2.0-to-3.0---COM-registration-tf4682182.html#a13408895
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] wix 2.0 to 3.0 - COM registration

2007-10-24 Thread Richard 

In article <[EMAIL PROTECTED]>,
"Nitin" <[EMAIL PROTECTED]>  writes:

> All my DLL's are .net assembly but they can be registered as COM.

Regasm /File will dump out a registry file of all the registry
values/keys that are needed to register your assembly.

Is there some tool in WiX that will eat a .reg file and turn it into
the necessary markup?
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
  

Legalize Adulthood! 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] wix 2.0 to 3.0 - COM registration

2007-10-24 Thread Strele Franz 
You can use the 'undocumented' "-scom" switch with heat.exe to generate only 
RegistryKey/RegistryValue-entries (instead of Class/ProgId/...).



> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] Im Auftrag von Strele Franz
> Gesendet: Mittwoch, 24. Oktober 2007 16:48
> An: wix-users@lists.sourceforge.net
> Betreff: Re: [WiX-users] wix 2.0 to 3.0 - COM registration
> 
> Using registry keys is the recommended way of registering .NET
> Assemblies for COM Interop.
> 
> http://msdn2.microsoft.com/en-us/library/aa367520.aspx
> 
> "Use the Registry table instead of the Class table when you register
> COM Interop for an assembly."
> 
> 
> > -Ursprüngliche Nachricht-
> > Von: [EMAIL PROTECTED] [mailto:wix-users-
> > [EMAIL PROTECTED] Im Auftrag von Karim MacDonald
> > Gesendet: Mittwoch, 24. Oktober 2007 16:26
> > An: wix-users@lists.sourceforge.net
> > Betreff: Re: [WiX-users] wix 2.0 to 3.0 - COM registration
> >
> >
> >
> > Nitin Chaudhari wrote:
> > >
> > > All my DLL's are .net assembly but they can be registered as COM.
> > >
> > Sorry, I should've looked more closely at your registry entries.
> FWIW,
> > here's my take on the problem:
> >
> > http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-
> on-
> > generated-registry-data-tf2815472.html#a13239912
> > http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-
> on-
> > generated-registry-data-tf2815472.html#a13239912
> >
> > I think that the problem is shared between heat.exe and candle.exe,
> and
> > came
> > to the conclusion that unless WiX is tweaked to specifically consider
> > COM-registerable .NET assemblies then large numbers of registry keys
> > end up
> > being the cleanest solution.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] wix 2.0 to 3.0 - COM registration

2007-10-24 Thread Strele Franz 
Using registry keys is the recommended way of registering .NET Assemblies for 
COM Interop.

http://msdn2.microsoft.com/en-us/library/aa367520.aspx

"Use the Registry table instead of the Class table when you register COM 
Interop for an assembly."


> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] Im Auftrag von Karim MacDonald
> Gesendet: Mittwoch, 24. Oktober 2007 16:26
> An: wix-users@lists.sourceforge.net
> Betreff: Re: [WiX-users] wix 2.0 to 3.0 - COM registration
> 
> 
> 
> Nitin Chaudhari wrote:
> >
> > All my DLL's are .net assembly but they can be registered as COM.
> >
> Sorry, I should've looked more closely at your registry entries. FWIW,
> here's my take on the problem:
> 
> http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-on-
> generated-registry-data-tf2815472.html#a13239912
> http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-on-
> generated-registry-data-tf2815472.html#a13239912
> 
> I think that the problem is shared between heat.exe and candle.exe, and
> came
> to the conclusion that unless WiX is tweaked to specifically consider
> COM-registerable .NET assemblies then large numbers of registry keys
> end up
> being the cleanest solution.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] wix 2.0 to 3.0 - COM registration

2007-10-24 Thread Karim MacDonald 


Nitin Chaudhari wrote:
> 
> All my DLL's are .net assembly but they can be registered as COM.
> 
Sorry, I should've looked more closely at your registry entries. FWIW,
here's my take on the problem:

http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-on-generated-registry-data-tf2815472.html#a13239912
http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-on-generated-registry-data-tf2815472.html#a13239912
 

I think that the problem is shared between heat.exe and candle.exe, and came
to the conclusion that unless WiX is tweaked to specifically consider
COM-registerable .NET assemblies then large numbers of registry keys end up
being the cleanest solution.
-- 
View this message in context: 
http://www.nabble.com/wix-2.0-to-3.0---COM-registration-tf4682182.html#a13384750
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] wix 2.0 to 3.0 - COM registration

2007-10-24 Thread Nitin 
All my DLL's are .net assembly but they can be registered as COM.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Karim
MacDonald
Sent: Wednesday, October 24, 2007 3:21 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] wix 2.0 to 3.0 - COM registration


Not a direct answer, but if you run WiX 3.0's heat.exe against your 32-bit
COM DLLs then it'll generate the right Class, AppID, Interface etc. output.
-- 
View this message in context:
http://www.nabble.com/wix-2.0-to-3.0---COM-registration-tf4682182.html#a1338
2551
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] wix 2.0 to 3.0 - COM registration

2007-10-24 Thread Karim MacDonald 

Not a direct answer, but if you run WiX 3.0's heat.exe against your 32-bit
COM DLLs then it'll generate the right Class, AppID, Interface etc. output.
-- 
View this message in context: 
http://www.nabble.com/wix-2.0-to-3.0---COM-registration-tf4682182.html#a13382551
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] wix 2.0 to 3.0 - COM registration

2007-10-23 Thread Nitin 
Hi,

 

I am trying to upgrade my WXS from wix 2.0 to 3.0, and I need some help with
the following components, 

 

This is what I had with wix 2.0 (I think it is plain COM registration),

 

  



















  

 

  























  

 

With wix 3.0, I believe we can do the following :

 

  



  



 

Will it work? And secondly how do I handle a dll which has 2 classes (abc.1
and abc.2)

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users