Apache log4net is distributed under the Apache License, version 2.0.
Starting with log4net 1.2.11 log4net is available as source only or binary only release.
Users who download the ZIP files to Windows may need to unblock the archive (right click on the ZIP and press the "Unblock" button) before extracting it.
We recommend you use a mirror to download our release builds, but you must verify the integrity of the downloaded files using signatures downloaded from our main distribution directories. Recent releases (48 hours) may not yet be available from the mirrors.
You are currently using [preferred]. If you
encounter a problem with this mirror, please select another
mirror. If all mirrors are failing, there are backup
mirrors (at the end of the mirrors list) that should be
available.
[if-any logo][end]
The KEYS link links to the code signing keys used to sign the product. The PGP link downloads the OpenPGP compatible signature from our main site. The MD5 link downloads the checksum from the main site.
| log4net-1.2.11-src.zip | md5 | pgp |
There are two different binary releases, oldkey and newkey. Both contain assemblies built for most supported platforms and have been built from the same code base, they only differ in the strong name key used to sign the assemblies.
See the FAQ for background. We recommend you use the assemblies signed with the "new" key whenever possible.
| log4net-1.2.11-bin-newkey.zip | md5 | pgp |
| log4net-1.2.11-bin-oldkey.zip | md5 | pgp |
The 1.2.10 and 1.2.9 releases have been created while log4net was still undergoing incubation and those releases are available from the Apache Software Foundation's distribution archive for the Incubator project.
Previous releases of log4net are available from the SourceForge Project Site.
It is essential that you verify the integrity of the downloaded files using the PGP signature or MD5 checksums. The checksums are not as strong indicators as the PGP signature.
Please read Verifying Apache HTTP Server Releases for more information on why you should verify our releases. The PGP keys used to sign our distributions are part of the KEYS file.