n-Tier Entity Framework (ntieref) still active? about remote.linq

[6bee]

Hi,
Thanks for your message.
Unfortunately ntieref is not actively maintained any longer. It has actually only been migrated from codeplex to ensure availability of the source code.
The main consideration for ntieref is the dependecy on the edmx, which you tipically don't have in code first scenarios. While ef migrations still use a form of the edmx model, it's never actually been tried out for ntieref and it would certainly cost some effort to make code generation work with somethimg else than EF6 model first.
In case it's fine to have control on defining the queries on client side, you may consider using Remote.Linq which makes building a data service tier very easy.
Hope ths helps.
Christof

[sdmckenna9]

Hi Christof, Thanks so much for your detailed response and advice. We will look into the Remote.Linq, and someone else mentioned we should check out Trackable Entities (https://github.com/TrackableEntities/trackable-entities). Your ntieref was a jewel, sir! =Steve= From: Christof Senn <[email protected]> Sent: Monday, July 16, 2018 6:48 PM To: 6bee/Remote.Linq <[email protected]> Cc: sdmckenna9 <[email protected]>; Author <[email protected]> Subject: Re: [6bee/Remote.Linq] n-Tier Entity Framework (ntieref) still active? (#39) Hi, Thanks for your message. Unfortunately ntieref is not actively maintained any longer. It has actually only been migrated from codeplex to ensure availability of the source code. The main consideration for ntieref is the dependecy on the edmx, which you tipically don't have in code first scenarios. While ef migrations still use a form of the edmx model, it's never actually been tried out for ntieref and it would certainly cost some effort to make code generation work with somethimg else than EF6 model first. In case it's fine to have control on defining the queries on client side, you may consider using Remote.Linq which makes building a data service tier very easy. Hope ths helps. Christof — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#39 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AnY_5GPm3vdSKqkD4VXymLqDruCGI1V-ks5uHRgZgaJpZM4VRlSo> . <https://github.com/notifications/beacon/AnY_5DiVutnlhboSw3V0NuNVPQvX-AOhks5uHRgZgaJpZM4VRlSo.gif>