LINQ Method cannot be translated into a store expression.

blog.dreamlabsolutions.com — A short snippet/workaround if you ever see the following exception: LINQ to Entities does not recognize the method ... , and this method cannot be translated into a store expression. It is thrown because in the Entity Framework Custom Methods & Extension Methods cannot be translated into a store expression. read more...

add a comment | category: Linq | Views: 13

Inheritance and Associations with Entity Framework Part 3

submitted by mosessaur 1 month, 21 days ago

mosesofegypt.net — On part 1 and part 2 I explored how to apply 2 different inheritance models (TPH & TPT) in Entity Framework. In this part I'm going to demonstrate associations between 2 base entities. And how to filter end properties to return specific type (sub entity). read more...

add a comment | category: Visual Studio | Views: 16

Inheritance and Associations with Entity Framework Part 1

submitted by mosessaur 1 month, 30 days ago

mosesofegypt.net — In this multi parts series I'll explore how to build inheritance with Entity Framework showing 2 different approaches of inheritance in Entity Framework. Beside that I'll show how to build simple association between 2 entities and show how to provide custom code to retrieve other parts of the relation when inheritance is applied. In this part I'm exploring Table-per-Hierarchy Inheritance model in EF read more...

add a comment | category: Visual Studio | Views: 35

Persistence Ignorance (POCO) Adapter for Entity Framework V1

blogs.msdn.com — One of the limitations of Entity Framework V1 released as part of .NET Framework 3.5 SP1 and Visual Studio 2008 SP1 is lack of support for POCO entity objects. POCO stands for Plain Old CLR Object and refers to an object that does not have any persistence concerns and is not aware of persistence framework. Modern development approaches such as DDD (Domain-Driven Design) and TDD (Test-Driven Development) prefer clear separation of concerns which implies persistence ignorance. [...] We have recently published a sample called EFPocoAdapter that includes code generator and a supporting library that implements POCO object tracking on top of Entity Framework V1 read more...

add a comment | category: Patterns | Views: 29

LINQ to Entities, Workarounds on what is not supported

submitted by mosessaur 2 months, 22 days ago

mosesofegypt.net — LINQ to Entities, Workarounds on what is not supported. 2 ways to get ride of what is not supported in LINQ to Entities. read more...

add a comment | category: Linq | Views: 26

Hidden Gems - Not the same old 3.5 SP1 post

submitted by crpietschmann 3 months, 9 days ago

hanselman.com — Folks were hassling me in the comments for not posting the picosecond that .NET 3.5 SP1 came out (or, as I like to call it, .NET 3.6 - although the bosses really don't like that). read more...

add a comment | category: CLR | Views: 15

ALT.NET Podcast 8 - EF Vote of No Confidence (part 2 of Episode 7)

published 4 months ago, submitted by powerrush 4 months, 1 day ago

altnetpodcast.com — In this episode Jeremy Miller and Ward Bell (from IdeaBlade) discuss the Vote of No Confidence on Microsoft's Entity Framework and what it means for the Alt.NET and .NET communities read more...

1 comment | category: Architecture | Views: 94

Paging and sorting the GridView control wih Entity Framework N Layer

emir.com.mx — Entity Framework is the best alternative of Microsoft for mapper a relational database to objects, and is already a very complete support in ASP.NET for populate the GridView control and enable the paging and sorting features directly by LinqDatasource object,but to use this alternative not have the chance to decouple the linq query in a business rules layer separated, which can be a problem if we have those requirements. The paging mut be done in the database for a more efficient query. read more...

add a comment | category: Linq | Views: 150