# Entity Framework - Tony Sneed's Blog
Tony Sneed's Blog
Trackable Entities project track changes to an object graph as you update, add and remove items, then send those changes to a back-end service where they can be saved in a single transaction.
|
The advantage of the consolidated designer is that you can pick and choose which tables you want, versus generating classes for all the tables in your database
|
I just completed a sample application using Simple MVVM Toolkit together with Trackable Entities to build a real-world N-Tier solution with a WPF client and portable POCO entities that are automatically change-tracked and sent to an ASP.NET Web API service that uses Entity Framework to perform asynchronous CRUD operations.
|
Taking a cue from Julie Lerman and Scott Hanselman, I've decided to dub version 2.0 of my Trackable Entities framework, the Ninja Edition.
|
With inquires on the project discussion forum, and some prompting by my friend Long Le, who authored the Generic Unit of Work and Repository Framework, I decided to add support to my framework for using Repository and Unit of Work design patterns.
|
In this blog post I'd like to perform an in-depth comparison between my own Trackable Entities framework and the now deprecated Self-Tracking Entities, written by the Entity Framework team at Microsoft.
|
I'd like to announce version 1.01 of Trackable Entities, which fixes a few issues and adds two methods to the API: AcceptChanges and MergeChanges
|
I am pleased to announce the release of Trackable Entities version 1.0 - with support for both WCF and ASP.NET Web API with Visual Studio 2012 and 2013!
|
Writing N-Tier apps can get complicated fast. Consider the assortment of n-tier technologies now consigned to the ash heap of history: WCF RIA Services, Self-Tracking Entities, and good old typed DataSets.
|
I recently delivered a free webinar for DevelopMentor on n-tier application development using Entity Framework 4.0.
|