Re: [WiX-users] outlook com addin

2007-11-28 Thread Szentpali Janos
As I previously said (though in  private mail) the solution is rather
simple:

SelfRegCost='1'

Anything else is just a waste of your life by overcomplicating simple
things and reinventing the wheel :D

János

Andrew Sampson wrote:
 I've had a similar problem - our Wise MSIs were previously using
 regasm/regsvr32 custom actions to register DLLs. In the switch to WiX
 though, I've written a CompilerExtension to get the registration info on
 compile and output it into the registry table of the generated MSI. It's
 fairly rough still, but seems to do the job well. It also handles ongoing
 development of the DLL - if the interfaces change or get added to, the new
 registration info is pulled in automatically the next time the MSI is built.


  

   _  

 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Chris Bardon
 Sent: Wednesday, 28 November 2007 3:45 AM
 To: Ben Reichelt; Ben
 Cc: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] outlook com addin

  

 Ben, I've created an installer for a C# COM addin using Wix, and I ran into
 some of the same problems.  The best way to get the necessary COM settings
 for a registration seems to be to use a registry sniffer that can compare
 snapshots.  I took a registry snapshot, registered the assembly, and then
 took another snapshot and grabbed the diff between the two.  Then I put all
 of these registry settings into my wxs file, and everything seemed to work.
 Probably not the most elegant solution, but another one that you can try
 out.  Just remember to try it on as clean a system as possible-a virtual PC
 is a good place to start.

  

 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Ben Reichelt
 Sent: Saturday, November 24, 2007 5:40 PM
 To: Ben
 Cc: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] outlook com addin

  

 I tried running heat on the directory with my .dlls and .ocxs, but it would
 just hang :(

 I tried the suggestion of setting the SelfRegCost='1' on each component and
 that did the trick, thanks for the replies. 

 ben

 On Nov 23, 2007 7:20 PM, Ben [EMAIL PROTECTED] wrote:

 Try running heat on a directory (not just a file)  that contains all the
 assemblies you need to register. 



 Ben Reichelt wrote: 

 I am making an installer for an Outlook vb6 COM addin.  The addin consists
 of 7 COM assemblies that need to be copied to the target machine and then
 have regsvr32 called on each assembly. I have read that calling out to
 regsvr32.exe from the msi is not recommended and instead you should manually
 create the registry keys needed for each assembly.

 The problem is that when I run heat.exe on my main assembly, it only
 generates a TypeLib wix element, not everything that is  needed to
 registry the assembly as an Outlook addin.  When I manually run regsvr32
 after installation, then the assembly is correctly added to Outlook.  I
 can't locate all the steps necessary to property register an assembly as an
 Outlook addin, so I can't do it manually at this point. 

 I have scoured the internet looking for someone else who has done this, but
 I can't find anyone. Does anyone have experience in making Outlook (or
 Office) addin installers?   Thanks

  
  





   _  



  
  
  
 -
 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
   

  

  


   
 

 -
 SF.Net email is sponsored by: The Future of Linux Business White Paper
 from Novell.  From the desktop to the data center, Linux is going
 mainstream.  Let it simplify your IT future.
 http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
 

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


-- 
Szentpáli János


-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] outlook com addin

2007-11-28 Thread John Hall
 As I previously said (though in  private mail) the solution is rather
 simple:
 
 SelfRegCost='1'
 
 Anything else is just a waste of your life by 
 overcomplicating simple things and reinventing the wheel :D

Except that the MSI documentation strongly suggests that you shouldn't:
Installation package authors are strongly advised against using self
registration. The remarks at the bottom of this page
[http://msdn2.microsoft.com/en-us/library/aa371608.aspx] contain a long
list of reasons.

Regards,
John

-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] outlook com addin

2007-11-28 Thread Szentpali Janos
John Hall wrote:
 As I previously said (though in  private mail) the solution is rather
 simple:

 SelfRegCost='1'

 Anything else is just a waste of your life by 
 overcomplicating simple things and reinventing the wheel :D
 

 Except that the MSI documentation strongly suggests that you shouldn't:
 Installation package authors are strongly advised against using self
 registration. The remarks at the bottom of this page
 [http://msdn2.microsoft.com/en-us/library/aa371608.aspx] contain a long
 list of reasons.

 Regards,
 John

   


-- 
Szentpáli János


-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] outlook com addin

2007-11-28 Thread Szentpali Janos
John Hall wrote:
 As I previously said (though in  private mail) the solution is rather
 simple:

 SelfRegCost='1'

 Anything else is just a waste of your life by 
 overcomplicating simple things and reinventing the wheel :D
 

 Except that the MSI documentation strongly suggests that you shouldn't:
 Installation package authors are strongly advised against using self
 registration. The remarks at the bottom of this page
 [http://msdn2.microsoft.com/en-us/library/aa371608.aspx] contain a long
 list of reasons.

 Regards,
 John

   
Sorry I forgot to paste the answer into the prev. reply. here it is:

Indeed, they (almost) all are the consequence of bad installer design or
bad programming habits... What can I say... good reasons indeed...
Nothing new under the sun as MS advices go.

-- 
Szentpáli János


-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] outlook com addin

2007-11-27 Thread Chris Bardon
Ben, I've created an installer for a C# COM addin using Wix, and I ran
into some of the same problems.  The best way to get the necessary COM
settings for a registration seems to be to use a registry sniffer that
can compare snapshots.  I took a registry snapshot, registered the
assembly, and then took another snapshot and grabbed the diff between
the two.  Then I put all of these registry settings into my wxs file,
and everything seemed to work.  Probably not the most elegant solution,
but another one that you can try out.  Just remember to try it on as
clean a system as possible-a virtual PC is a good place to start.

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ben
Reichelt
Sent: Saturday, November 24, 2007 5:40 PM
To: Ben
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] outlook com addin

 

I tried running heat on the directory with my .dlls and .ocxs, but it
would just hang :(

I tried the suggestion of setting the SelfRegCost='1' on each component
and that did the trick, thanks for the replies. 

ben

On Nov 23, 2007 7:20 PM, Ben [EMAIL PROTECTED] wrote:

Try running heat on a directory (not just a file)  that contains all the
assemblies you need to register. 



Ben Reichelt wrote: 

I am making an installer for an Outlook vb6 COM addin.  The addin
consists of 7 COM assemblies that need to be copied to the target
machine and then have regsvr32 called on each assembly. I have read that
calling out to regsvr32.exe from the msi is not recommended and instead
you should manually create the registry keys needed for each assembly.

The problem is that when I run heat.exe on my main assembly, it only
generates a TypeLib wix element, not everything that is  needed to
registry the assembly as an Outlook addin.  When I manually run regsvr32
after installation, then the assembly is correctly added to Outlook.  I
can't locate all the steps necessary to property register an assembly as
an Outlook addin, so I can't do it manually at this point. 

I have scoured the internet looking for someone else who has done this,
but I can't find anyone. Does anyone have experience in making Outlook
(or Office) addin installers?   Thanks







 

-
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


Re: [WiX-users] outlook com addin

2007-11-24 Thread Ben Reichelt
I tried running heat on the directory with my .dlls and .ocxs, but it would
just hang :(

I tried the suggestion of setting the SelfRegCost='1' on each component and
that did the trick, thanks for the replies.

ben

On Nov 23, 2007 7:20 PM, Ben [EMAIL PROTECTED] wrote:

  Try running heat on a directory (not just a file)  that contains all the
 assemblies you need to register.



 Ben Reichelt wrote:

 I am making an installer for an Outlook vb6 COM addin.  The addin consists
 of 7 COM assemblies that need to be copied to the target machine and then
 have regsvr32 called on each assembly. I have read that calling out to
 regsvr32.exe from the msi is not recommended and instead you should
 manually create the registry keys needed for each assembly.

 The problem is that when I run heat.exe on my main assembly, it only
 generates a TypeLib wix element, not everything that is  needed to
 registry the assembly as an Outlook addin.  When I manually run regsvr32
 after installation, then the assembly is correctly added to Outlook.  I
 can't locate all the steps necessary to property register an assembly as an
 Outlook addin, so I can't do it manually at this point.

 I have scoured the internet looking for someone else who has done this,
 but I can't find anyone. Does anyone have experience in making Outlook (or
 Office) addin installers?   Thanks

 --

 -
 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 [EMAIL 
 PROTECTED]://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


Re: [WiX-users] outlook com addin

2007-11-23 Thread Thomas Leigh
At this point, it doesn't really matter whether your COM assembly is for 
Outlook or not.

The problem you have is that you need to know the Class Ids, Prog Ids, Type 
Libs, etc of each of your COM assemblies. Because you used VB6 to create your 
assemblies, all this info is hidden from you and you probably aren't even 
aware that it exists, let alone how it all fits together.

Once you've read some tutorials on COM and understand how it works, you should 
be able to answer your own question J


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben Reichelt
Sent: 23 November 2007 20:55
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] outlook com addin

I am making an installer for an Outlook vb6 COM addin.  The addin consists of 7 
COM assemblies that need to be copied to the target machine and then have 
regsvr32 called on each assembly. I have read that calling out to regsvr32.exe 
from the msi is not recommended and instead you should manually create the 
registry keys needed for each assembly.

The problem is that when I run heat.exe on my main assembly, it only generates 
a TypeLib wix element, not everything that is  needed to registry the 
assembly as an Outlook addin.  When I manually run regsvr32 after installation, 
then the assembly is correctly added to Outlook.  I can't locate all the steps 
necessary to property register an assembly as an Outlook addin, so I can't do 
it manually at this point.

I have scoured the internet looking for someone else who has done this, but I 
can't find anyone. Does anyone have experience in making Outlook (or Office) 
addin installers?   Thanks
-- This message has been scanned for viruses by Sophos PureMessage.
-
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] outlook com addin

2007-11-23 Thread Ben Reichelt
I am making an installer for an Outlook vb6 COM addin.  The addin consists
of 7 COM assemblies that need to be copied to the target machine and then
have regsvr32 called on each assembly. I have read that calling out to
regsvr32.exe from the msi is not recommended and instead you should manually
create the registry keys needed for each assembly.

The problem is that when I run heat.exe on my main assembly, it only
generates a TypeLib wix element, not everything that is  needed to
registry the assembly as an Outlook addin.  When I manually run regsvr32
after installation, then the assembly is correctly added to Outlook.  I
can't locate all the steps necessary to property register an assembly as an
Outlook addin, so I can't do it manually at this point.

I have scoured the internet looking for someone else who has done this, but
I can't find anyone. Does anyone have experience in making Outlook (or
Office) addin installers?   Thanks
-
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] outlook com addin

2007-11-23 Thread Ben
Try running heat on a directory (not just a file)  that contains all the 
assemblies you need to register.




Ben Reichelt wrote:
I am making an installer for an Outlook vb6 COM addin.  The addin 
consists of 7 COM assemblies that need to be copied to the target 
machine and then have regsvr32 called on each assembly. I have read 
that calling out to regsvr32.exe from the msi is not recommended and 
instead you should manually create the registry keys needed for each 
assembly.


The problem is that when I run heat.exe on my main assembly, it only 
generates a TypeLib wix element, not everything that is  needed to 
registry the assembly as an Outlook addin.  When I manually run 
regsvr32 after installation, then the assembly is correctly added to 
Outlook.  I can't locate all the steps necessary to property register 
an assembly as an Outlook addin, so I can't do it manually at this point.


I have scoured the internet looking for someone else who has done 
this, but I can't find anyone. Does anyone have experience in making 
Outlook (or Office) addin installers?   Thanks



-
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