FYI,
Just wanted to share this email I rec'd this morning. This issue in question
deals with .net 3.5 client profile builds on log4net which I briefly tried
looking at last fall. Looks like another solution has been suggested. Dunno
if it will go anywhere though. Here's to hoping.. :)
Thanks,
Ryan
Begin forwarded message:
> From: "Jon S Akhtar (JIRA)" <j...@apache.org>
> Date: May 16, 2011 7:35:48 AM PDT
> To: rmbo...@gmail.com
> Subject: [jira] [Commented] (LOG4NET-174) log4net.dll references assemblies
> that are not part of the .NET 3.5 SP1 client profile
>
>
> [
> https://issues.apache.org/jira/browse/LOG4NET-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034031#comment-13034031
> ]
>
> Jon S Akhtar commented on LOG4NET-174:
> --------------------------------------
>
> I just added a CLIENT define, and placed it in the correct 7 locations
> usually "!NETCF && !SSCLI && !CLIENT".
>
> This builds a client profile version of the assembly. I think that it follows
> the methodology used to handle the other platform cases, so I don't really
> see it being a major problem design-wise.
>
>
>> log4net.dll references assemblies that are not part of the .NET 3.5 SP1
>> client profile
>> --------------------------------------------------------------------------------------
>>
>> Key: LOG4NET-174
>> URL: https://issues.apache.org/jira/browse/LOG4NET-174
>> Project: Log4net
>> Issue Type: Bug
>> Components: Builds
>> Affects Versions: 1.2.10
>> Environment: .Net 3.5 SP1
>> Reporter: Kuno Meyer
>>
>> .Net 3.5 SP1 / VS 2008 SP1 has a new build feature: the "client-only
>> framework subset" switch in the projects settings, meaning that the
>> developer can specify that only a limited subset of the .Net framework is
>> used. This helps in reducing the size of installers that include the .Net
>> framework.
>> Unfortunately, log4net.dll (1.2.10) has references to System.Web, which is
>> not part of this "client-only framework subset". This leads to the following
>> compilation warning:
>> <<<
>> C:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets : warning
>> MSB3253: The referenced assembly "log4net, Version=1.2.10.0,
>> Culture=neutral, PublicKeyToken=1b44e1d426115821,
>> processorArchitecture=MSIL" has a dependency on "System.Web,
>> Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which is
>> not listed as part of the "Client" TargetFrameworkSubset. If this dependent
>> reference is required, you may get compilation errors.
>>>>>
>> My proposal is to split log4net.dll into a new log4net.dll (core+generic
>> appenders) and into a separate appender DLL (log4net.server.dll) for
>> deployment on servers only.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
