Return-Path: Delivered-To: apmail-logging-log4net-user-archive@www.apache.org Received: (qmail 48981 invoked from network); 30 Oct 2008 14:04:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Oct 2008 14:04:57 -0000 Received: (qmail 60728 invoked by uid 500); 30 Oct 2008 14:05:02 -0000 Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org Received: (qmail 60432 invoked by uid 500); 30 Oct 2008 14:05:01 -0000 Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4NET User" List-Id: Delivered-To: mailing list log4net-user@logging.apache.org Received: (qmail 60421 invoked by uid 99); 30 Oct 2008 14:05:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Oct 2008 07:05:01 -0700 X-ASF-Spam-Status: No, hits=3.1 required=10.0 tests=HTML_EXTRA_CLOSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [68.142.200.119] (HELO web30506.mail.mud.yahoo.com) (68.142.200.119) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 30 Oct 2008 14:03:45 +0000 Received: (qmail 38981 invoked by uid 60001); 30 Oct 2008 14:04:24 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=csNmwfJp/MTU9OLYTzbHHsMsSm4gn3wZgpWnWITe1tySqmtsBXEZY1r4RgWQODIjpXJwJ6UxdJH5hsFiURs4UaN9/QJdgWeD6/607k9ir6aWoAuxZwYeZOrM0FpY20Vmj/Fdfw/MxguQfm5qWsa7Uc1kbQGjFda90s4q23MKU28=; X-YMail-OSG: 8wu.WwoVM1lEzNQww6khdR2tTtSTSGKSavRK2NQbMbYuS74Snbzjg4lR3AaExJzbyGblpuOWXdcW0DxjUEB4b4fnZO_TIWleVVGi8MB3JvsLLikZmleuC4SPXIKkS4fQU_rM8I.CFUNmTQS94Fy8UVmiZBvAxYD99YRjy7mBWo0Ar305kOXzrxickM4A Received: from [64.207.14.125] by web30506.mail.mud.yahoo.com via HTTP; Thu, 30 Oct 2008 07:04:23 PDT X-Mailer: YahooMailWebService/0.7.247.3 Date: Thu, 30 Oct 2008 07:04:23 -0700 (PDT) From: hdjim69 Reply-To: hdjim69@yahoo.com Subject: RE: when to use strong name confusion To: Log4NET User In-Reply-To: <43A10173A6B4F54BACFACFB39EBD47553312EB@ex2.techsoftwareinc.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-883219418-1225375463=:38726" Message-ID: <537107.38726.qm@web30506.mail.mud.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org --0-883219418-1225375463=:38726 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Yes, this is for internal use.=A0 We are not a vendor. However we have seve= ral projects in the solution (VS2005) that need to log (client.exe, client.= dll, server.dll, etc.).=A0 I just want to be able to go into each project a= nd add a reference to the log4net.dll and that should do it.=A0 No GAC just= a reference in each project to the log4net.dll.=20 =A0 Is this the correct way to set up referencing this .dll? --- On Thu, 10/30/08, Walden H. Leverich wrote: From: Walden H. Leverich Subject: RE: when to use strong name confusion To: "Log4NET User" , hdjim69@yahoo.com Date: Thursday, October 30, 2008, 9:45 AM Is this for _internal_ use? IOW, you're not a ISV getting ready to distribu= te software, right? In that case, just ignore strong names completely. Use = the DLL as it, and don't worry about sn.exe or signing at all. Except in ra= re cases (and you'll know when you get there) there is no point in using st= rongly named assemblies internally.=20 =A0 If you're an ISV, then consider it, but then you'll have to understand stro= ng names for your own stuff and the log4net stuff will seem obvious. =A0 -Walden =A0 --=20 Walden H Leverich III Tech Software (516) 627-3800 x3051 WaldenL@TechSoftInc.com http://www.TechSoftInc.com =A0 Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) =A0 From: hdjim69 [mailto:hdjim69@yahoo.com]=20 Sent: Thursday, October 30, 2008 8:54 AM To: log4net-user@logging.apache.org Subject: when to use strong name confusion =A0 Hello,=20 =A0 Not sure I understand the strong name requirements.=A0 I'm on .Net 2.0.=A0 = There is already a .dll in the log4net-1.2.10\bin\net\2.0 dir. Do I need to= rebuild this .dll with a strong name key or can I just use this dll as it = is ?=A0=A0=A0 I know what a strong name is and how to generate a private/pu= blic key but still not sure how this relates to when and why I would need t= o do this with log4net. =A0 =A0 Any help would be appreciated. =A0 =A0 TIA J =A0=0A=0A=0A --0-883219418-1225375463=:38726 Content-Type: text/html; charset=us-ascii
Yes, this is for internal use.  We are not a vendor. However we have several projects in the solution (VS2005) that need to log (client.exe, client.dll, server.dll, etc.).  I just want to be able to go into each project and add a reference to the log4net.dll and that should do it.  No GAC just a reference in each project to the log4net.dll.
 
Is this the correct way to set up referencing this .dll?


--- On Thu, 10/30/08, Walden H. Leverich <WaldenL@TechSoftInc.com> wrote:
From: Walden H. Leverich <WaldenL@TechSoftInc.com>
Subject: RE: when to use strong name confusion
To: "Log4NET User" <log4net-user@logging.apache.org>, hdjim69@yahoo.com
Date: Thursday, October 30, 2008, 9:45 AM

Is this for _internal_ use? IOW, you're not a ISV getting ready to distribute software, right? In that case, just ignore strong names completely. Use the DLL as it, and don't worry about sn.exe or signing at all. Except in rare cases (and you'll know when you get there) there is no point in using strongly named assemblies internally.

 

If you're an ISV, then consider it, but then you'll have to understand strong names for your own stuff and the log4net stuff will seem obvious.

 

-Walden

 

--

Walden H Leverich III

Tech Software

(516) 627-3800 x3051

WaldenL@TechSoftInc.com

http://www.TechSoftInc.com

 

Quiquid latine dictum sit altum viditur.

(Whatever is said in Latin seems profound.)

 

From: hdjim69 [mailto:hdjim69@yahoo.com]
Sent: Thursday, October 30, 2008 8:54 AM
To: log4net-user@logging.apache.org
Subject: when to use strong name confusion

 

Hello,

 

Not sure I understand the strong name requirements.  I'm on .Net 2.0.  There is already a .dll in the log4net-1.2.10\bin\net\2.0 dir. Do I need to rebuild this .dll with a strong name key or can I just use this dll as it is ?    I know what a strong name is and how to generate a private/public key but still not sure how this relates to when and why I would need to do this with log4net.

 

 

Any help would be appreciated.

 

 

TIA

J

 


--0-883219418-1225375463=:38726--