- Current Releases
- Older Releases
ELMAH 1.2 SP2
There are several ways to download ELMAH 1.2 Service Pack (SP) 2. You can either grab the fat archives containing everything you might ever need or go for leaner ones if you think you know exactly what you need.
ELMAH, SQLite & 32-bit vs. 64-bit
ELMAH itself is independent of processor architecture (i.e. pure managed code). However, it becomes important to distinguish between 32-bit (x86) and 64-bit (x64) environments for archives and deployments that include the SQLite driver binary.
The fat downloads with most of what you might ever need are:
|Binaries (x86)||Binaries for deploying to a 32-bit (x86) environment running .NET Framework 1.x, 2.0 or a later version. This archive includes debug builds, samples, dependencies and scripts. Source code is not included.|
|Binaries (x64)||Binaries for deploying to a 64-bit (x64) environment running .NET Framework 1.x, 2.0 or a later version. This archive includes debug builds, samples, dependencies and scripts. Source code is not included.|
|Sources||Source files for development. Use this for private builds or to contribute fixes and enhancements back to the project. See [Compiling] for more help.|
If all you want is the ELMAH assembly for Microsoft .NET Framework 2.0 or a later version then download one of the core binary archives below. The core binary includes built-in support for logging errors to memory, loose XML files, Microsoft Access, Microsoft SQL Server and Oracle.
|Core Binary||Stand-alone ELMAH binary, including Program Database (PDB) file.|
|Core Binary (debug)||Stand-alone debug build of ELMAH, including Program Database (PDB) file. Use of debug build is recommended if you are developing on top of ELMAH and want maximum debugging support. It not recommended for production use because it prevents the JIT compiler from making optimizations.|
|Sample web.config||Sample web.config file that illustrates how to configure the various options. It can be handy for necessary sections relevant for your own
If you downloaded the core binary then you may need additional driver binaries from below depending on the database you choose for logging errors. These binaries go alongside
Elmah.dll. You will also need to download a DDL script for creating database objects.
|Database||Driver Binaries||DDL Script||Notes|
|Microsoft Access||Included in .NET Framework||MS Access DDL (WSH) Script||The DDL script is also embedded in ELMAH. You may need it if you don’t have sufficient rights to create the database at runtime.|
|Microsoft SQL Server||Included in .NET Framework||MS SQL Server DDL Script||-|
|MySQL||MySQL Binaries||MySQL DDL Script||-|
|Oracle||Included in .NET Framework 2.0+||Oracle DDL Script||-|
|PostgreSQL||PostgreSQL Binaries||PostgreSQL DDL Script||-|
|SQLite||SQLite (x86) or SQLite (x64)||Embedded in ELMAH||There is no separate DDL script available for download.
|Microsoft SQL Server Compact (SSCE) 4.0||See section on private deployment in SQLServerCompact||Embedded in ELMAH||There is no separate DDL script available for download.
The quickest way to get started with ELMAH is to use one of the following NuGet packages that already contain the necessary binaries, as well as initial configuration for ASP.NET applications and various backing error log stores:
- elmah.corelibrary: Just the library without any configuration
- elmah: ELMAH with initial configuration for its ASP.NET modules and handlers
- elmah.xml: Configuration for logging to stand-alone XML files
- elmah.sqlqerver: Configuration for logging to a Microsoft SQL Server (2000 or later)
- elmah.sqlservercompact: Configuration for logging to a Microsoft SQL Server Compact database
- elmah.access: Configuration for logging to a Microsoft Access database
- elmah.mysql: Configuration for logging to a MySQL 5.0+ database
- elmah.oracle: Configuration for loggin to an Oracle database
- elmah.postgresql: Configuration for logging to a PostgreSQL database
Don’t forget to also check-out the many packages on NuGet that build on top of ELMAH.