Entity Framework Extensions (EFExtensions) Project available in CodeGallery

When I announced the start of the Entity Framework Toolkits & Extensions section in CodeGallery, Colin already had a big chunk of what he is now making available in the works. And so I had it in my mind when I defined the Entity Framework Toolkits & Extensions as a collection of source code and tools to augment EF's capabilities and extend its reach to new scenarios.

It took Colin 2 months to get some free time (readying a product for release is no easy task), to write some extra functionality (the custom materializer was first introduced a couple of weeks ago) and to get his code properly reviewed, etc.

I would like to recommend you to go and download EFExtensions from the project page at CodeGallery, and then enjoy Colin's first blog post explaining some of the stuff the current EFExtensions are good for.

By the way, one of my my favorite parts of the project is the EntitySet class and its GetTrackedEntities() method 🙂

Alex already introduced Colin as one super smart colleague. In fact, I cannot stress enough how smart Colin is. He is the uber developer. But I must add that intelligence is not his only quality!

Please, send us feedback on this. The most straightforward way is to use the Discussion tool in CodeGallery, but feel free to use the email links in our blogs.

And expect some really cool new EF Tools & Extensions form Colin and other members of the team. I know what I am talking about! 🙂

Comments (1)
  1. Aloysius says:

    Hello Diego,

    I’m trying to use Entity Framework Extensions to build by Data access Layer as it seems very promising in regard to materializing objects directly from stored procedures. I’ve done the following steps and was wondering where I’ve gone wrong.

    Therefore firstly I have created a data object from the EF model and removed all its table mapping. I have mapped my stored procedures to the Insert, Update and Delete mappings of the data object.

    For the list, "get" stored procedure from the EF using CreateStoreCommand, and materializing it to data objects (using EF Extenstions). Now I want to attach it to the objectcontext to allow EF to handle concurrency, which means If i bind this context to the grid, the changes made to the grid should be saved (using the mapped stored procedures).

    Here the problem is, when I try to attach the objects to the object context, it dosen’t seem to do the job, i end up with no objects in the objectcontext. I use the objectContext.AttachTo(<<EntitySet name>>, <DataObject>)

    Please advice, any help on this would be greatly appriciated.

Comments are closed.

Skip to main content