RE: Any plans for an MSI package?

19 Jul 2004 14:09:44 -0000

Title: Message

Jiho is correct, an MSI needs to have a unique, but consistent GUID.  The only way I can see this being acceptable is if the Apache Group offered an MSI for the Log4Net package.  I’m not sure if the MSM is a similar situation as an MSM isn’t a standalone component (the MSM is meant to be merged with other components to create an MSI.) 

 

-Michael

 

From: Jiho Han [mailto:[EMAIL PROTECTED]
Sent: Monday, July 19, 2004 10:06 AM
To: Log4NET User; [EMAIL PROTECTED]
Subject: RE: Any plans for an MSI package?

 

Matthew,

 

I still haven't deployed log4net to the GAC.  And as another person pointed out, the .dll is already signed so installing into the GAC is not a problem.

As you may already know, the issue is with a standardized way of installing to the GAC.  I am not all that familiar with MSI/MSMs but from what I read, each component should have a unique but consistent guid.  And if every one and their uncle created a MSI package using their own generated GUI to install log4net, I don't think the result would be too pleasing.

 

I also read somewhere that MSMs have their own problems as well and so I was hoping whether log4net community would create an official MSI package for people like us.  I would definitely share any findings I have.

Let me know if you have other suggestions.

Thanks

 

Jiho

-----Original Message-----
From: Matthew Easlea [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 14, 2004 11:53 PM
To: 'Log4NET User'
Subject: RE: Any plans for an MSI package?

Jiho,

 

I’m wondering how you went deploying Log4Net.dll into the GAC.

I have found some references to using Strong Names in the log4net code, but I haven’t seen any documentation in the FAQ about how to install log4net into the GAC. Did you have to recompile log4net to be able to install it into the GAC?

 

And if you have created a merge module for log4net it would be excellent if you could share it with the community.

 

Cheers

 

Matthew James Easlea

 

 

From: Jiho Han [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 22 June 2004 1:48 AM
To: Log4NET User
Subject: RE: Any plans for an MSI package?

 

I am using WiX toolset to create my MSI package and from what I can tell, it's as easy as changing <Product> tag to <Module> tag.

 

Here's a link to the project website:

 

-----Original Message-----
From: Chad Myers [mailto:[EMAIL PROTECTED]
Sent: Monday, June 21, 2004 11:42 AM
To: Log4NET User
Subject: RE: Any plans for an MSI package?

Actually, log4net should ship with both an MSI for itself and an merge module to include in other installations.

 

The MSI is pretty easy, but I don’t know much about merge modules.

 

-c

 

From: Jiho Han [mailto:[EMAIL PROTECTED]
Sent: Monday, June 21, 2004 9:45 AM
To: [email protected]
Subject: Any plans for an MSI package?

 

I need to deploy log4net to the GAC and I am looking to make this part of an overall MSI package.  Is there an MSI distribution for log4net?

I would include it as part of my MSI package.  However, in discussing this on various windows installers newsgroups, I've been told that the best way to approach this is for the producer of the component to provide an MSI.

It's sort of like why one should obtain a Primary Interop Assembly from the manufacturer for a COM component if you are going to use one in your .NET project.

I would volunteer to do it but I'm a newbie to the whole installer thing myself.

Any ideas?
Thanks

Jiho Han

Reply via email to