Log4net
  1. Log4net
  2. LOG4NET-174

log4net.dll references assemblies that are not part of the .NET 3.5 SP1 client profile

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: 1.2.10
    • Fix Version/s: None
    • Component/s: Builds
    • Labels:
      None
    • Environment:
      .Net 3.5 SP1

      Description

      .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.

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Kuno Meyer
            • Votes:
              18 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development