Nope, it was mostly annoying as it wouldn't respect shared POCO libraries, that is to say the proxy generator itself would extend those classes instead of just resolving them as-is ... so if you had a client and server all pulling the same DLL for the entity objects, it wouldn't work as cleanly. You then had to write a DataContract resolver on your own to handle the lookups to ensure you had one DAL to rule them all.
That and I find most code-gen solutions from MSFT team to be too mickey mouse, despite my repeated warnings that they should stop this foolishness. --- Regards, Scott Barnes http://www.riagenic.com On Sat, Apr 14, 2012 at 7:28 PM, Greg Keogh <g...@mira.net> wrote: > ie I've written a small code-gen tool that basically will inspect a basic > POCO and then spit out some code that produces something like this inside > my DbContext class.**** > > ** ** > > How do you feel about the EF 4.x POCO Entity Generator? Didn’t it suit > your needs?**** > > ** ** > > I’ve only used the Self-Tracking template, not the POCO one. However, out > of curiosity I just generated some code with the POCO template to see what > it looks like, and it’s pretty “plain” with no dependencies upon anything > in System.Data.**** > > ** ** > > Greg**** >
