Andrew,

Log4net 1.2.0-beta8 has the [assembly: System.CLSCompliant(true)]
attribute set in the AssemblyInfo.cs file.
The release builds are signed with a strong name.

Cheers,

Nicko 

> -----Original Message-----
> From: Andrew Elmhorst [mailto:[EMAIL PROTECTED] 
> Sent: 24 September 2004 17:54
> To: Log4Net Group
> Subject: Signing and ClsCompliant
> 
> Has anyone on this list requested or talked about signing 
> log4net and making it CLSCompliant?
> 
>  
> 
> If not, please add these features to the list of requests. 
> These should be easy to implement.
> 
>  
> 
> 1.    Add the CLSCompliant attribute to the AssemblyInfo.cs 
> file. I did this with my sources here and it built with no 
> code changes. 
>       Justification: Any developer developing an assembly 
> that is dependent on log4net and exposes log4net objects in 
> public APIs will not be able to mark those APIs as 
> CLSCompliant unless log4net itself is marked as CLSCompliant.
> 2.    Create a private key and sign any official builds of 
> log4net with the key. 
>       Justification: Any developer developing a signed 
> component based upon log4net cannot compile until they 
> rebuild log4net and sign it. It would be nice if official 
> builds of log4net were signed so that component developers 
> could use the official builds.
> 
>  
> 
> Regards,
> 
>  
> 
> Andrew Elmhorst
> 
> Senior Software Engineer
> 
> Edustructures, LLC
> 
> 

Reply via email to