logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Walden H. Leverich" <Wald...@TechSoftInc.com>
Subject RE: when to use strong name confusion
Date Thu, 30 Oct 2008 13:45:19 GMT
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 H Leverich III

Tech Software

(516) 627-3800 x3051


http://www.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




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.






View raw message