[prev in list] [next in list] [prev in thread] [next in thread]
List: log4net-user
Subject: RE: Any plans for an MSI package?
From: "Jiho Han" <jhan () InfinityInfo ! com>
Date: 2004-06-21 15:48:27
Message-ID: 52BB2995616A314BA1DE65030F9B258966843E () infsrv02 ! infinityinfo ! com
[Download RAW message or body]
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:
http://sourceforge.net/projects/wix/
-----Original Message-----
From: Chad Myers [mailto:chad@chadmyers.com]
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:jhan@InfinityInfo.com]
Sent: Monday, June 21, 2004 9:45 AM
To: log4net-user@logging.apache.org
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
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1264" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Verdana;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New \
Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto }
SPAN.EmailStyle18 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><SPAN class=282594615-21062004><FONT face=Verdana color=#800000 size=2>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.</FONT></SPAN></DIV>
<DIV><SPAN class=282594615-21062004><FONT face=Verdana color=#800000
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=282594615-21062004><FONT face=Verdana color=#800000
size=2>Here's a link to the project website:</FONT></SPAN></DIV>
<DIV><SPAN class=282594615-21062004></SPAN> </DIV>
<DIV><SPAN class=282594615-21062004><FONT face=Verdana color=#800000 size=2><A
href="http://sourceforge.net/projects/wix/">http://sourceforge.net/projects/wix/</A></FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Chad Myers
[mailto:chad@chadmyers.com] <BR><B>Sent:</B> Monday, June 21, 2004 11:42
AM<BR><B>To:</B> Log4NET User<BR><B>Subject:</B> RE: Any plans for an MSI
package?<BR><BR></FONT></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Actually, log4net
should ship with both an MSI for itself and an merge module to include in
other installations.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: \
Arial"><o:p> </o:p></SPAN></FONT></P> <P class=MsoNormal><FONT face=Arial \
color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: \
Arial">The MSI is pretty easy, but I don’t know much about merge \
modules.<o:p></o:p></SPAN></FONT></P> <P class=MsoNormal><FONT face=Arial color=navy \
size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: \
Arial"><o:p> </o:p></SPAN></FONT></P> <P class=MsoNormal><FONT face=Arial \
color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: \
Arial">-c<o:p></o:p></SPAN></FONT></P> <P class=MsoNormal><FONT face=Arial \
color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: \
Arial"><o:p> </o:p></SPAN></FONT></P> <DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: \
Tahoma">From:</SPAN></FONT></B><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: \
10pt; FONT-FAMILY: Tahoma"> Jiho Han [mailto:jhan@InfinityInfo.com] <BR><B><SPAN
style="FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, June 21, 2004 9:45
AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B>
log4net-user@logging.apache.org<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> Any plans for an MSI
package?</SPAN></FONT><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P><FONT face=Verdana size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">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?</SPAN></FONT><o:p></o:p></P>
<P><FONT face=Verdana size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">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.</SPAN></FONT><o:p></o:p></P>
<P><FONT face=Verdana size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">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.</SPAN></FONT><o:p></o:p></P>
<P><FONT face=Verdana size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">I would volunteer to do it but
I'm a newbie to the whole installer thing myself.</SPAN></FONT>
<o:p></o:p></P>
<P><FONT face=Verdana size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">Any ideas?</SPAN></FONT>
<BR><FONT face=Verdana size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">Thanks</SPAN></FONT>
<o:p></o:p></P>
<P><FONT face=Verdana size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana">Jiho Han</SPAN></FONT>
<o:p></o:p></P></DIV></BLOCKQUOTE></BODY></HTML>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic