[
https://issues.apache.org/jira/browse/LOG4NET-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922473#action_12922473
]
Kuno Meyer commented on LOG4NET-174:
------------------------------------
As opposed to my original request two years ago, I think that splitting
log4net.dll into several assemblies isn't an option. (Due to handling
convenience, backwards compatibility and XML configuration issues.)
Therefore, a better way might be to provide multiple build versions of
log4net.dll, one for each environment:
- .NET 2.0 / 4.0 full installation (the same file as today)
- .NET 3.5 SP+ / 4.0 client profile (a stripped-down version)
- (is the compact framework an option? does it need special treatment?)
> 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.
-
You can reply to this email to add a comment to the issue online.
