- Taschenbuch: 280 Seiten
- Verlag: Apress; Auflage: 1st ed. (7. Dezember 2009)
- Sprache: Englisch
- ISBN-10: 159059990X
- ISBN-13: 978-1590599907
- Größe und/oder Gewicht: 21,6 x 1,6 x 26 cm
- Durchschnittliche Kundenbewertung: 1 Kundenrezension
- Amazon Bestseller-Rang: Nr. 953.835 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
- Komplettes Inhaltsverzeichnis ansehen
Pro Entity Framework 4.0 (Expert's Voice in .NET) (Englisch) Taschenbuch – 7. Dezember 2009
|Neu ab||Gebraucht ab|
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
Explaining how to effectively utilize the integration between SQL Server and.NET 3.5 in SQL Server 2008, this handbook offers detailed coverage of the LINQ and ADO.NET Entity Framework, SQLCLR architecture, .NET development, LINQ to SQL, how to implement the Entity Framework, practical applications, and more. Original. (Intermediate/Advanced).
Über den Autor und weitere Mitwirkende
Jim Wightman is a Microsoft trained and certified technical specialist with over 25 years of experience. A key technical advisor, solution provider, developer, innovator, and inventor for clients throughout the UK, USA, and Saudi Arabia, Jim currently specializes in OLTP and OLAP database design and development. Most recently, he has concentrated particularly on engineering SQL Server 2005 toolset solutions to hold and manipulate multiple-terabyte, massive-throughput databases for law enforcement and intelligence use.
Derzeit tritt ein Problem beim Filtern der Rezensionen auf. Bitte versuchen Sie es später noch einmal.
Die hilfreichsten Kundenrezensionen auf Amazon.com
The book is good for presenting the basic ideas behind the EF and how to use it. The book did improve my understanding of EF.
Unfortunately, the approach taken is very much a "step by step" guide showing each and every screenshot of what the UI should look like as you work your way through different wizards and scenarios. The trouble is that UI changed even before the book was published. The book was written to a beta version of Visual Studio 2010 despite being officially published after Visual Studio 2010 Release Candidate was released. Those who want a detailed guide will get frustrated at the "treat the user like an idiot and show him every screenshot" approach taken (presumably to help pad the page count out) while those who like this style will quickly get frustrated because the screenshots don't reflect any kind of reality as too much has been changed since the beta.
Apress publish some great books, but this isn't one of them. My guess is that it's been rushed to market to cash in on the demand for information before what most consider "the bible" (Julie Lehrman's O'Reilly book) gets updated to the latest version. Clearly Julie and her publishers have more integrity, waiting until the product is "fully baked" before rushing out a book on the product. And certainly her "Version 1" book on the same subject had far more depth and detail than this slim, introductory volume does.
I regret buying this book, and would strongly urge others to avoid doing so. Wait for the O'Reilly book, or an alternative that reflects the reality of what you'll have to work with, rather than an early beta.
I read it all from beginning to end and got some usefulness out of it. Maybe not expert level but more than beginner for sure.
However, one thing that pissed me off were the blunders - the author apparently wanted to unleash a new book ASAP, and forgot to review and correct mistakes. This is unacceptable for professionals writing books, moreover for APRESS.
I am usually attentive to such things and write down the mistakes when I note them in books and send out to authors so they correct in next editions. But with this book I just stopped recording them.. it was too much..
I'll post some of them hereunder, for you to be informed:
1) The Object set class (the class name in fact is ObjectSet)
2) This line establishes and manages our database connection and provides >>>of<<< the functionality of
working with entity data as objects as well as managing object state. (who's that "of"?)
3) In this chapter you have >>>a<<< seen a few LINQ-to-Entities queries (who's that "a"?)
4) first, I you need to discuss the Model Browser window (I or you?)
5) You’re not finished: you need the WriteLinecodeto show the write information. (not "write" but "right"!)
6) because you want access to the context at the form level so that you can save, delete, and delete. (save, update and delete)
1) This first example selects everyone with a first name of King or a first name of Jones, (the example is about last names and not first names)
2) • SSDL: Storage Schema Definition Language, also known as the conceptual model
• CSDL: Conceptual Schema Definition Language, also known as the storage model
(mixed one another's description)
3) Although denoted by “0..1” (which means “zero or one”) this can be misinterpreted. This
simply means that one Person might have multiple Employee roles, but only one employee can be
related to a single Person. (The explanation is a disaster. 0..1 relationship never means multiple)
4) Take a look at the Schemaelement. The Namespace includes “.Store” (it includes "Model.Store" and not ".Store")
5) OK, now on to the CSDL. (author starts about MSL and not CSDL)
6) however, keep in mind that IQueryable inherits from ObjectQuery (goodness.... ObjectQuery implements IQueryable!)
7) When you added stored procedures to the EDM, the SOAP Service Description Language (SSDL)represents the stored procedures as functions. (What does SOAP Service Description Language have to do with SSDL in EF?!?! SSDL stands for Storage Schema Definition Language which has been noted throughout the book! Where did you seize the SOAP from?)