ADO.NET Entity Framework Extensions

NEW POST: SPROC with Out-parameter

EDVGradl — Thu, 02 Jul 2009 12:04:47 GMT

Hi!
I am beginning to use EFExtensions, because i need to call SPROCs in my database. All is fine, but i have many SPROC with OUT parameters. Wenn i call a SPROC with EFExtensions i get an exception like this:
Procedure or function 'aSPROC' expects parameter '@aOutParam', which was not supplied. But this parameter is an out-parameter. When i supply this parameter i get nothing returned :-(
How can I achieve this problem?

Thanks!

NEW POST: Using Materializer with dynamic field set

parheric — Mon, 29 Jun 2009 15:33:40 GMT

Was hoping to get some guidance for using materializers with dynamic fields returned.

Calling a proc that returns search results, but depending on the search options, certain columns may/may not be returned in the results set.
Is there a preferred method to populate an entity using a func<t1,t2> without having to create a different materializer for each 'shaped' result set?

the only 'neat' way that I've found to do this is too pass a idatareader into the constructor of the entity, however I still haven't found a way to detect if a field actually exists in the result set.

UPDATED RELEASE: EF Extensions Visual Studio 2008 SP1 (Aug 12, 2008)

Fri, 22 May 2009 19:27:20 GMT

This updated version of the extensions library targets the Visual Studio 2008 SP1. Changes include:

* Helpers simplifying getting and setting key values for EntityReferences.

2009-22-5 update:

* Sample project now available in VB

2008-12-7 update:

* Bug fix: using *ObjectContext.CommandTimeout* in calls to *CreateCommand*.
* Sample project now illustrates use of *EntityReference* properties when materializing results.
* New helper method overloads have been added to support *InvocationExpression* in LINQ queries and expressions.

UPDATED RELEASE: EF Extensions Visual Studio 2008 SP1 (Aug 12, 2008)

Fri, 22 May 2009 19:26:12 GMT

This updated version of the extensions library targets the Visual Studio 2008 SP1. Changes include:

* Helpers simplifying getting and setting key values for EntityReferences.

2008-12-7 update:

* Bug fix: using *ObjectContext.CommandTimeout* in calls to *CreateCommand*.
* Sample project now illustrates use of *EntityReference* properties when materializing results.
* New helper method overloads have been added to support *InvocationExpression* in LINQ queries and expressions.

NEW POST: How do I install the extension?

EAlmeida — Thu, 26 Feb 2009 16:49:44 GMT

Sorry, but I don't find how do I install the extension.
Thanks for any help :)

NEW POST: can't get sample to run

balq60 — Thu, 12 Feb 2009 20:15:52 GMT

I run the darn thing and there are NO parameters setup to pass in when you run this.

I know it's looking for the connectgion string, so I added that as a parameter, but still no luck.

It would be nice, if for once, when I download an example from Microsoft, it would work...

NEW POST: DefaultShaper with EntityKey for

emikelsoft — Tue, 03 Feb 2009 21:34:21 GMT

Is it possible to extend the DefaultShaper to include the entitykeys of all relations of an entity?

thx, emikelsoft

UPDATED WIKI: Home

cmeek — Sun, 07 Dec 2008 17:22:50 GMT

The ADO.NET Entity Framework Extensions library includes utilities that make querying stored procedures, creating typed results from DB data readers and state tracking external data much easier in the Entity Framework. A sample application demonstrates several patterns using these utilities, including stored procedures with multiple result sets, materialization of CLR types, and registering entities in the Entity Framework state manager.

Overview

Utilities are included to simplify:

Execution of store commands via the ObjectContext.
Connection lifetime management.
State management of entities from external sources.
Materialization of arbitrary CLR types given a data reader or DB command.
Stored procedure mapping:

Multiple result sets.
Column renames, polymorphic results and nested structures via the materialization service.

Getting and setting key values for entity references.
Rewrite InvocationExpressions in LINQ queries and expressions.

Requirements

Visual Studio 2008 SP1.

http://msdn.microsoft.com/en-us/vsts2008/products/cc533447.aspx

Other resources

The following post introduces the EFExtensions API and includes a walkthrough of the sample application:

http://blogs.msdn.com/meek/archive/2008/03/26/ado-entity-framework-stored-procedure-customization.aspx

For additional information on multiple result sets and relationships, see:

http://blogs.msdn.com/meek/archive/2008/12/07/stored-procedures-and-first-class-relationships-in-the-entity-framework.aspx

For additional information on InvocationExpression rewriting, see:

http://blogs.msdn.com/meek/archive/2008/12/07/invocationexpression-and-linq-to-entities.aspx

UPDATED RELEASE: EF Extensions Visual Studio 2008 SP1 (Aug 12, 2008)

Sun, 07 Dec 2008 16:43:37 GMT

This updated version of the extensions library targets the Visual Studio 2008 SP1. Changes include:

* Helpers simplifying getting and setting key values for EntityReferences.

2008-12-7 update:

* Bug fix: using *ObjectContext.CommandTimeout* in calls to *CreateCommand*.
* Sample project now illustrates use of *EntityReference* properties when materializing results.
* New helper method overloads have been added to support *InvocationExpression* in LINQ queries and expressions.

UPDATED RELEASE: EF Extensions Visual Studio 2008 SP1 (Aug 12, 2008)

Sun, 07 Dec 2008 16:41:38 GMT

This updated version of the extensions library targets the Visual Studio 2008 SP1. Changes include:

* Helpers simplifying getting and setting key values for EntityReferences.

2008-12-7 update:

* Bug fix: using *ObjectContext.CommandTimeout* in calls to *CreateCommand*.
* Sample project now illustrates use of *EntityReference* properties when materializing results.
* New helper method overloads have been added to support *InvocationExpression* in LINQ queries and expressions.

NEW POST: EFExtensions does not work well with VB.NET

PJonDevelopment — Wed, 26 Nov 2008 20:13:33 GMT

Never mind my previous post, I forgot to add the Microsoft.Data.Extensions namespace as an Import.

Paulo Santos
http://pjondevelopment.50webs.com

NEW POST: EFExtensions does not work well with VB.NET

PJonDevelopment — Wed, 26 Nov 2008 18:38:17 GMT

Hi,

The EFExtensions does not work as extension methods when used with VB.NET.

All the static methods needed to be called as they are and not as extensions as they should.

Regards,

Paulo Santos
http://pjondevelopment.50webs.com

NEW POST: Does the EF model requires the Data Objects to be mapped to a table?

Pranav — Thu, 21 Aug 2008 23:39:05 GMT

There is a feature called ModificationFunctions which allow you would use your own stored procs that map to InsertFunction, DeleteFunction and UpdateFunction. This way your entities are still mapped to the tables but the logic to do any CRUD operations is overridden by your sprocs.

Here is an example I have from my edmx file:
[EFMappingFileSamples > ModificationFunctions
In SSDL:
<Schema Namespace="exp.Store" Alias="Self" ...
...
<Function Name="usp_CreateExperiment" Aggregate="false" BuiltIn="false" NiladicFunction="false" IsComposable="false" ParameterTypeSemantics="AllowImplicitConversion" Schema="dbo">
<Parameter Name=“experiment_id” Type="varchar" Mode="In" />
<Parameter Name="description" Type="varchar" Mode="In" />
</Function>
<Function Name="usp_UpdateExperiment" …
<Function Name="usp_DeleteExperiment" …

In MSL:
<EntitySetMapping Name="Experiments">
<EntityTypeMapping TypeName="exp.Experiment">
...
<ModificationFunctionMapping>
<InsertFunction FunctionName="exp.Store.usp_CreateExperiment">
<ScalarProperty Name=“experimentid” ParameterName=“experimentid” />
<ScalarProperty Name="description" ParameterName="description" />
<AssociationEnd AssociationSet="FKcontroltreatment" From="Experiment" To="Treatment">
<ScalarProperty Name=“experimentid” ParameterName=“experimentid” />
</AssociationEnd>
</InsertFunction>
<DeleteFunction …
<UpdateFunction …
</ModificationFunctionMapping>
<AssociationSetMapping Name=" FKcontroltreatment" TypeName="exp.FKexperimentscontrol_treatment" StoreEntitySet="experiments">
<EndProperty Name="treatments">
<ScalarProperty Name="treatmentid" ColumnName="controltreatment" />
</EndProperty>
<EndProperty Name="Experiment">
<ScalarProperty Name="experimentid" ColumnName="experimentid" />
</EndProperty>
<Condition ColumnName="control_treatment" IsNull="false" />
<ModificationFunctionMapping>
<InsertFunction FunctionName="exp.Store.uspCreateExperimentJunk">
<EndProperty Name="Experiment">
<ScalarProperty Name="experimentid" ParameterName="experimentid"/>
</EndProperty>
<EndProperty Name="Treatment">
<ScalarProperty Name="treatmentid" ParameterName="treatmentid"/>
</EndProperty>
</InsertFunction>
<DeleteFunction….
</ModificationFunctionMapping>
</AssociationSetMapping>

Note:
1. If one modification function mapping is created for an entity all the 3 should be created i.e InsertFunction, DeleteFunction, UpdateFunction. Also any associations related to this entity should also have modification functions for InsertFunction and DeleteFunction.
2. StoredProcs for InsertFunction, DeleteFunction and UpdateFunction cannot be exact same. But it is possible to put a dummy stored proc that does not exist in database as long as that function is not invoked.

UPDATED WIKI: Home

cmeek — Tue, 12 Aug 2008 19:54:35 GMT

Overview

Utilities are included to simplify:

Execution of store commands via the ObjectContext.
Connection lifetime management.
State management of entities from external sources.
Materialization of arbitrary CLR types given a data reader or DB command.
Stored procedure mapping:

Multiple result sets.
Column renames, polymorphic results and nested structures via the materialization service.

Getting and setting key values for entity references.

Requirements

Visual Studio 2008 SP1.

http://msdn.microsoft.com/en-us/vsts2008/products/cc533447.aspx

Other resources

CREATED RELEASE: EF Extensions Visual Studio 2008 SP1 (Aug 12, 2008)

Tue, 12 Aug 2008 19:52:09 GMT

This updated version of the extensions library targets the Visual Studio 2008 SP1. Changes include:

* Helpers simplifying getting and setting key values for EntityReferences.

NEW POST: Does the EF model requires the Data Objects to be mapped to a table?

aloysius — Tue, 12 Aug 2008 09:41:09 GMT

I'm looking at Entity Framework (EF) for building my Data Access Layer as it seems promising with the requirement I have. My requirement is to use stored procedures (for get, add, update, delete) and allow EF to handle concurrency. Also to achieve this, I do not want the data objects I've created to be mapped to tables as the stored procedures would do the job for me to get and save the data.

I'm not sure if this is possible as I'm unable to save the data if the data object is not mapped. Please advice.

Thanks,

UPDATED RELEASE: EFExtensions Visual Studio 2008 SP1 Beta (May 13, 2008)

Tue, 13 May 2008 21:11:53 GMT

This updated version of the extensions library targets the Visual Studio 2008 SP1 Beta. Changes include:

* A strict version of the default materializer which requires a column for every member of an EDM structural type.
* Shaper delegate optimizations.

UPDATED WIKI: Home

cmeek — Tue, 13 May 2008 21:11:20 GMT

Overview

Utilities are included to simplify:

Execution of store commands via the ObjectContext.
Connection lifetime management.
State management of entities from external sources.
Materialization of arbitrary CLR types given a data reader or DB command.
Stored procedure mapping:

Multiple result sets.
Column renames, polymorphic results and nested structures via the materialization service.

Requirements

Visual Studio 2008 SP1 Beta 1.

http://msdn.microsoft.com/en-us/vstudio/cc533448.aspx

Other resources

UPDATED RELEASE: EFExtensions Visual Studio 2008 SP1 Beta 1 (May 13, 2008)

Tue, 13 May 2008 21:04:03 GMT

This updated version of the extensions library targets Visual Studio 2008 SP1 Beta 1. Changes include:

* A strict version of the default materializer which requires a column for every member of an EDM structural type.
* Shaper delegate optimizations.

UPDATED RELEASE: EFExtensions Entity Framework Beta 3 (Mar 24, 2008)

Tue, 13 May 2008 21:03:17 GMT

Initial release. Includes utilities simplifying custom stored procedure and store command calls. This release targets the Entity Framework Beta 3.