O'Reilly has told me that Kindle is coming but I have no idea when and I doubt they will give me, a lowly author ;), a target date. OReilly has ebooks (pdf, mobi which translates to kindle and one other) avail on their site. (Sorry amazon)
Got tired of waiting for my hard copy from Safari, so I ordered another one from Amazon. Arrives tomorrow. This is one book I won't mind having two copies of. One for my office, and one for home. EF4 is really making my data access tasks SO much easier, and this book is so clear and easy to understand!
Julia, that's great news, thanks! The final push for me to buy the Kindle DX was actually the fact I wanted your book, and I have no access to a book store here on the east side of PR. Time to stop crafting TSQL statements and JOINs, I guess.
@Walter: That's cool to hear. If you haven't bought the kindle yet, Amazon can thank me for encouraging you to buy it if you do it through my associate account. :) On the learnentityframework.com site, just follow the "buy book from Amazon" link and anything you get on amazon that way, gets me a pat on the back from amazon ...which I can translate into a beer or a cup of coffee at Starbucks. :)
Thanks for reading the post and noticing, I realized that I had the wrong edition when I saw two copies of the book on the Kindle and the one I was reading required .Net 3.5, not 4.0. Now I have just one (2nd edition) and a refund in the mail.
Julia. I do have a technical question. I know this is not the proper forum, and if you'd like me to ask this somewhere else, I'll be happy to do that, but since I have your attention... Really, my one and only grievance with EF4 is keeping the model in sync with the data store. Maybe I haven't given it enough of a chance, but, but "model first" doesn't seem to be practical when developing new applications around existing, mature databases. When we are in "development mode" on a real project, schema changes can be fast and furious. "Refreshing the model from the database" is a pretty crude way of dealing with these issues. It's really not much better than the LINQ2SQL design surface where you have to delete the table, and drag it back on model. I'm surprised there has not been more effort in this area. I've been using a third party sync utility that seems to work pretty darn well, but is that really how MS envisions these sorts of tools to evolve? If you are interested, the tool is: http://www.huagati.com/dbmltools/ very nice.