Entity Framework 4 (in a legacy upgrade)

2010-12-16 Thread Greg Keogh
We've been playing with EF4 for a few days to see if it is a good candidate as a 'data layer' in a project that is being upgraded from VB6. As Kirsten said a couple of days ago, she has some VB6 classes that represent tables and there are stored procs to load and save the classes. She would like to

Re: Entity Framework 4 (in a legacy upgrade)

2010-12-16 Thread Nathan Schultz
I'm not familiar with netTiers, but does it support things such as lazy loading? What's it's LINQ support like? Caching? Change Tracking? In its simplest form EF4 can act like a code generation tool, creating an object hierarchy from the database. But that's not the only approach you can take. You

RE: Entity Framework 4 (in a legacy upgrade)

2010-12-16 Thread Greg Keogh
>but does it support things such as lazy loading? I don't think so. >What's it's LINQ support like? It's not a LINQ provider, you can just use LINQ to objects/collections as usual. >Caching? Yes, but it's irritating and I turn it off. >Change Tracking? Yes. I like the wa

RE: Entity Framework 4 (in a legacy upgrade)

2010-12-16 Thread Greg Keogh
Ooops, I forgot to mention... I created a sanity test app that makes a model out of a CE 3.5 database with a dozen joined tables and it seems to be working without any glitches at all. I just added all the tables, it made a lovely default model diagram and classes, then a Forms app can load a t

Re: Entity Framework 4 (in a legacy upgrade)

2010-12-16 Thread Scott Barnes
EF is ok for when you have a simplistic CRUD situation whereby you feed data on a per table basis, it does however get a bit murky and cumbersome when you have linked tables and such, as then its a case of "you better know EF like the back of your hand before you proceed" type moments. I personally

Re: C# to Delphi

2010-12-16 Thread Peter Maddin
After sleeping on it, I thought that in stead of a dll or COM server, why not just write an executable and start it from my c# code. I can pass any start-up requirements as command line parameters . I would not have any problems with state management. I could communicate with the process usin

Re: C# to Delphi

2010-12-16 Thread Matt Siebert
Glad to hear you had some success with the sample code. Not sure if it helps, but if you can't keep a reference to anything global in the Delphi dll, then maybe you could just pass a pointer back and forth - i.e. pass the data from .NET to Delphi initially and have the Delphi code allocate the mem