Merge pull request #116 from apache/Feature/v2.0.16

Release notes for 2.0.16
diff --git a/NOTICE b/NOTICE
index 468a2f5..eaab50a 100644
--- a/NOTICE
+++ b/NOTICE
@@ -1,5 +1,5 @@
    Apache log4net
-   Copyright 2004-2022 The Apache Software Foundation
+   Copyright 2004-2024 The Apache Software Foundation
 
    This product includes software developed at
    The Apache Software Foundation (https://www.apache.org/).
diff --git a/doc/BUILDING.md b/doc/BUILDING.md
index aeff9f6..87d0491 100644
--- a/doc/BUILDING.md
+++ b/doc/BUILDING.md
@@ -1,11 +1,36 @@
 ## Building log4net
 
 Log4net provides support for a wide array of targets, including
-- older .net 2 and 3.5 (including client profiles)
+- older .net 2 and 3.5 (including client profile for net-40)
 - more modern net40/net45
 - netstandard1.3/2.0
 
 As such, it does require a relatively full .net environment on Windows to build.
+I have recently found a fairly freshly-installed win11 machine to work adequately,
+after adding the "windows feature" for ".NET Framework 3.5 (includes .NET 2.0 and 3.0)"
+
+TL;DR (Windows):
+- install Visual Studio Build Tools (at least VS2019)
+- install nodejs (at least v16)
+- install dotnet (v7+) and the .NET SDK (current latest)
+- install dotnet 2, 3, 3.5 via "add windows features"
+- in the project folder:
+  - `npm i`
+  - `npm run build`
+
+TL;DR (!Windows):
+- install the dotnet SDK - v7 or better (at time of writing, v8 is current but
+  I've had some issues elsewhere, so I'm waiting a bit before recommending it
+  everywhere
+- install Mono (you're going to need it to target certain versions of .NET)
+- install nodejs 16+
+  - in the project folder:
+  - `npm i`
+  - `export DOTNET_CORE=1 npm run build`
+    - we force using `dotnet` on non-windows targets for now. At some point,
+      this should become automatic
+
+## The full story
 
 Options:
 - build locally. Suggested environment:
@@ -35,6 +60,10 @@
             - `npm run build`
             - optionally `npm test` to run all tests
             - optionally `npm run release` to generate release artifacts
+- build locally (CLI edition)
+  - install nodejs (at least v16)
+  - `npm i`
+  - `npm run build`
 - build via docker for windows, using the `build-with-docker-for-windows.bat` script
 - build via the vs2019 Windows AppVeyer image. There is an appveyer.yml file
     included which (should) build if you set up AppVeyer to track
diff --git a/src/log4net/log4net.csproj b/src/log4net/log4net.csproj
index 015b505..61dfe5a 100644
--- a/src/log4net/log4net.csproj
+++ b/src/log4net/log4net.csproj
@@ -73,13 +73,6 @@
     <RemoveIntegerChecks>false</RemoveIntegerChecks>
     <Deterministic>true</Deterministic>
   </PropertyGroup>
-  <PropertyGroup Condition="'$(TargetFramework)'=='net35-client'">
-    <TargetFrameworkIdentifier>.NETFramework</TargetFrameworkIdentifier>
-    <TargetFrameworkVersion>v3.5</TargetFrameworkVersion>
-    <TargetFrameworkProfile>Client</TargetFrameworkProfile>
-    <OutDir>..\..\build\$(Configuration)\net35-client</OutDir>
-    <DefineConstants>$(DefineConstants);NET_2_0;NET_3_5;CLIENT_PROFILE</DefineConstants>
-  </PropertyGroup>
   <PropertyGroup Condition="'$(TargetFramework)'=='net40-client'">
     <TargetFrameworkIdentifier>.NETFramework</TargetFrameworkIdentifier>
     <TargetFrameworkVersion>v4.0</TargetFrameworkVersion>
@@ -213,4 +206,4 @@
       <ReferenceCopyLocalPaths Include="@(ReferenceCopyLocalPaths->'%(RootDir)%(Directory)%(Filename).xml')" Condition="'%(ReferenceCopyLocalPaths.NuGetPackageId)' != '' and Exists('%(RootDir)%(Directory)%(Filename).xml')"/>
     </ItemGroup>
   </Target>
-</Project>
\ No newline at end of file
+</Project>