Entity Framework Pitfalls: Registering Custom Database Functions for LINQ

Like I said in my previous post, it’s not enough to add a DbFunctionAttribute attribute to a method to have it call a database function. If the function is not a built-in one, it will not be registered in the Entity Framework provider manifest for SQL Server, so it will require registration in the model. You might think, just by looking at the methods in SqlFunctions that all that it took was to add this attribute, but you would be wrong.

See a brief explanation by the EF team here.


No Comments

Add a Comment

As it will appear on the website

Not displayed

Your website