Elmah.Contrib.EntityFramework

Provides the way to integrate Elmah with Microsoft ADO.NET Entity Framework. Initially written in F# but then rewritten in C#.

Description

You may want not to keep in Web.config both connection strings for Entity Framework (used by your project) and for SQL Server (used by Elmah.SqlServer) duplicating each other. The goal of this library is to extract the underlying provider connection string from the EF connection string so only one will be kept in Web.config.

Also you can query Elmah errors table using LINQ to Entities having strongly-typed POCO entities.

Comments and contributions are very welcome!

Examples

With Model/Database First approach:

<configuration>
	<connectionStrings>
		<add name="ModelContainer" connectionString="metadata=res://*/;provider=System.Data.SqlClient;provider connection string=&quot;Data Source=localhost;Initial Catalog=Northwind;Integrated Security=True;&quot;" providerName="System.Data.EntityClient" />
	</connectionStrings>
	<elmah>
		<errorLog type="Elmah.Contrib.EntityFramework.EntityErrorLog, Elmah.Contrib.EntityFramework" connectionStringName="ModelContainer" />
	</elmah>
</configuration>

With Code First approach. To query for existing errors:

var elmahContext = new ElmahContext(nameOrConnectionString);
var errors = await elmahContext.Errors.ToArrayAsync();

You can also optionally specify the table name to map:

var elmahContext = new ElmahContext(nameOrConnectionString, tableName: "MyElmahErrorsTable");

Or the schema name, or both:

var elmahContext = new ElmahContext(nameOrConnectionString, schemaName: "audit");

To add new error:

elmahContext.Errors.Add(
	new ElmahError
	{
	});
await elmahContext.SaveChangesAsync();

Remarks

With the same connection string, you can use either EntityErrorLog (requires providerName="System.Data.EntityClient") or EntityContext (requires providerName="System.Data.SqlClient") but not both.