That was my experience with EF also. First thing I tried (a few years back now) was to get 'plug-able databases' working. I.e. Target sqlite or SQL server based on configuration change. The consensus on forums was to create two parallel sets of EF classes and wrap them both in a custom interface (which I would have to define and write the wrapper code for). Definitely a 'get off the bus and walk' moment for me.
Ado.net or linq2sql get the job done. On 01/02/2011, at 8:01 AM, "Greg Keogh" <[email protected]> wrote: > I've ordered the other book on EF4 that was mentioned yesterday. After > reading the Learman book for many weeks, I find when I sit down to code that > the very first seemingly simple and fundamental thing I want to do is > obscure or impossible. The books and magazine articles never prepare you for > what will happen in a real app. > > EF4 has shocking up-front difficulty barrier to using it in a serious app. > It seems that you need a PhD in EF4ology before you can get started. > > If and when I eventually do get EF4 working to my satisfaction I will report > on it, and I'll report on the two EF4 books. > > It's not Friday, but as an aside: You are the only second person I have ever > heard use the word 'greenfields'. A colleague used it two days ago and I > thought he was talking about a company called Green Fields. Is this another > Americanism creeping into our language? Or is it from some other discipline? > My current pet hate is the word "impacts". My latest IT books (including > Lerman's) are using it everywhere in sentences like "setting this option > will impact performance". Will the word "affect" be deprecated from the > English language? Even the ABC news and local newspapers are now reporting > how "this will impact that". I'm surprised I can't hear all of these > collisions. > > I'll have to dogfood the impact and architect a solution before we verbize > anymore nouns. > > Greg >
