• Alle Preisangaben inkl. MwSt.
Nur noch 7 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon.
Geschenkverpackung verfügbar.
Menge:1
Dependency Injection in N... ist in Ihrem Einkaufwagen hinzugefügt worden
Gebraucht: Sehr gut | Details
Verkauft von Warehouse Deals
Zustand: Gebraucht: Sehr gut
Kommentar: Gebrauchsspuren. Kleiner Fleck oder geringe Abnutzung auf der Vorderseite. Kleine Falte oder kleiner Knick auf der Rückseite. Kleiner Schnitt oder Kratzer auf dem Buchrücken. Kleiner Fleck oder geringe Abnutzung auf den Seiten. Amazon-Kundenservice und Rücknahmegarantie (bis zu 30 Tagen) bei jedem Kauf.
Ihren Artikel jetzt
eintauschen und
EUR 6,00 Gutschein erhalten.
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Anhören Wird wiedergegeben... Angehalten   Sie hören eine Probe der Audible-Audioausgabe.
Weitere Informationen
Alle 2 Bilder anzeigen

Dependency Injection in NET (Englisch) Taschenbuch – 6. Oktober 2011


Alle Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Amazon-Preis Neu ab Gebraucht ab
Taschenbuch
"Bitte wiederholen"
EUR 32,95
EUR 29,83 EUR 20,78
67 neu ab EUR 29,83 8 gebraucht ab EUR 20,78

Wird oft zusammen gekauft

Dependency Injection in NET + The Art of Unit Testing: With Examples in C# + C# in Depth
Preis für alle drei: EUR 95,00

Die ausgewählten Artikel zusammen kaufen

Kunden, die diesen Artikel gekauft haben, kauften auch

Jeder kann Kindle Bücher lesen — selbst ohne ein Kindle-Gerät — mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.


Produktinformation

  • Taschenbuch: 552 Seiten
  • Verlag: Manning; Auflage: 1 (6. Oktober 2011)
  • Sprache: Englisch
  • ISBN-10: 1935182501
  • ISBN-13: 978-1935182504
  • Größe und/oder Gewicht: 18,7 x 3,3 x 23,5 cm
  • Durchschnittliche Kundenbewertung: 4.0 von 5 Sternen  Alle Rezensionen anzeigen (2 Kundenrezensionen)
  • Amazon Bestseller-Rang: Nr. 21.736 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)

Mehr über den Autor

Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Produktbeschreibungen

Über den Autor und weitere Mitwirkende

Mark Seemann is a professional software developer and architect living in Copenhagen, Denmark. He has been working with software since 1995 and TDD since 2003, including six years with Microsoft as a consultant, developer and architect. Since 2009, Mark has been an architect with Safewhere.

Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?


In diesem Buch (Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Hier reinlesen und suchen:

Kundenrezensionen

4.0 von 5 Sternen
5 Sterne
0
4 Sterne
2
3 Sterne
0
2 Sterne
0
1 Sterne
0
Beide Kundenrezensionen anzeigen
Sagen Sie Ihre Meinung zu diesem Artikel

Die hilfreichsten Kundenrezensionen

4 von 4 Kunden fanden die folgende Rezension hilfreich Von Cavigelli Matthias am 8. Mai 2012
Format: Taschenbuch
Ich habe das Buch gekauft um mehr über den DI Container von Spring.Net zu erfahren. Über Dependency Injection an sich hatte ich mir nicht systematisch Gedanken gemacht.

Das Buch ist nach der Einführung in drei Teile aufgegliedert.
In der Einführung wird an Hand eines Beispiels eine echte Schichtung einer Applikation durchgezogen.
Der erste Teil (DI Catalog) besteht aus (Anti-)Patterns und zugehörigen Refactorings.
Im zweiten Teil wird versucht sich der Autor an einem eigenen DI Container. Dabei erläutert er die Herausforderungen.
Im dritten und letzten Teil werden verschiedene Container vorgestellt. Ich habe mich nur für den Spring Container interessiert.

Das Buch ist sehr umfangreich. Es ist sicherlich sehr systematisch gegliedert. Die Patterns werden hergeleitet und begründet. Allerdings ist eben auch unnötig lange, es enthält viele Wiederholungen oder auch Duplikationen.
Der Leseaufwand kann gesenkt werden, wenn nur der erste Teil (DI Catalog) gelesen wird.

Aus meiner Sicht stechen die Refactorings und einzelne Patterns wie Composition Root heraus.
Ob man einen Container verwendet oder eine Eigenkonstruktion, Lesende werden ihren Code nach der Buchlektüre loser gekoppelt schreiben.
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
2 von 2 Kunden fanden die folgende Rezension hilfreich Von Marius Goppelt VINE-PRODUKTTESTER am 25. Februar 2014
Format: Taschenbuch Verifizierter Kauf
Worum geht es? Teils um eine Philosophie, teils um eine Technologie wie man mittelgroße bis sehr große Software strukturiert.

Der Autor schreibt selbst: bei den meisten Lesern fällt der Groschen so ungefähr ab Seite 100. Bis dahin ist das Buch ein zäher Knochen, an dem man lange rumkauen muss. Das hängt zum einen damit zusammen, dass seine Beispiele nicht immer ganz glücklich gewählt sind. Zumindest ich dachte mir bei vielen Abschnitten "das ist doch totaler Overkill", oder "ist das nicht eine Lösung für ein Problem was ohne diese Lösung gar nicht existieren würde?"
Zum anderen verliert er sich gerade zu Anfang ganz gerne in theoretischen Erörterungen, die er erst wesentlich später mit konkreten Beispielen unterfüttert.

Mein persönlicher Groschen fiel, als ich vor einem realen Problem saß: ich hatte eine eigentlich relativ kleine Webanwendung, die im laufenden Betrieb (und nur dort) sporadisch seltsame Fehler zeigte. Über ein Jahr habe ich daran rumgefrickelt, und habe keinen rechten Weg gefunden wie ich denn systematisch die Anwendung testen soll, ohne den laufenden Betrieb zu gefährden. Dieses Buch half mir dabei, neu über mein Problem nachzudenken, und Stück für Stück die Anwendung in kleinere, kontrollierbarere und letztendlich testbarere Komponenten aufzusplitten.

Selbst wenn man nicht die zentrale Botschaft des Buches übernimmt ("Verwende gefälligst ein Dependency Injection Framework!"), fängt man neu an über Softwarearchitektur nachzudenken.

Wenn man über eins der Frameworks wie Spring.
Lesen Sie weiter... ›
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen

Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)

Amazon.com: 50 Rezensionen
42 von 42 Kunden fanden die folgende Rezension hilfreich
No Adjectives Left 6. September 2012
Von David Foley - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
The Short Story: This is the best software development book I have ever read. By miles. Or, in deference to Mr. Seeman, in kilometers. Stop. Buy this book. It will change how you think, how you reason, how you sleep at night. See you in a year, we will both be smarter.

The Long Story: I bought this book last year. I can't remember exactly why I bought it, but I suspect that it had something to do with intellectual intimidation and the frightening title. I come from a non-OO background, but I am too young to get through the next 20 years without dealing with the reality of OO prevalence in small (i.e. numerous) projects. I had 2 choices ... start at the bottom or start at the top. Believe me, I chose the latter with this book.

I'm not going to explain the content in every chapter, simply because other reviewers have already done the job as I would have. Read Mr. T. Anderson's fine review if you need that kind of detail. Instead, I will talk about the effect that this book had had on how I think.

Chapter 2 is the velvet sledgehammer in the face. I read along with the case study, nodding my head and exercising my (in retrospect, tiny) brain as Seeman describes how "Mary" and "Jens" go about building a layered application. I'm thinking, yes Mary and Jens, this is what the magazines, blog articles, and dime-a-dozen gurus are saying regarding the construction of layered application. Seeman then dissects the "layered" application. Actually, he doesn't dissect it; he tears it to shreds and stamps all over it. Brilliantly. It's truly scary to read this chapter. You will feel like a complete novice at the end of it. You then have two choices ... (1) reject this stuff as abstract, ivory tower nonsense, or (2) put on your big-boy-pants.

Having lived with this book for almost a year, this is how I suggest you use it:
1. Read from Part 1 through Part 3.
2. Stop. Think. Cry at how embarrassed you feel at the end of Part 1 Chapter 2.
3. Read Part 2 again.
4. Stop. Think. Cry at how happy you feel now that you've lifted yourself beyond 99% of .NET developers. Beyond 99% of software professionals, period.
5. Do some "poor-man's DI" exercises.
6. Read only the introductory sections of each chapter within Part 4.
7. Pick a DI container in Part 4 that appeals to you based on the previous bullet, read its Part 4 chapter, and spend 1-2 months playing with it.
8. Revisit Parts 2 and 3 on a regular basis as references.
9. Don't think about sauces or Fowlerisms.

Criticisms: Very, very, few. I do not think it's too "wordy" at all. Any repetition is done with the realization that this stuff is really, really, hard for most of us. But yes, any mention of nonsense about "Anemic Domain Models" normally sets my blood boiling and warrants an immediate docking of at least 1 star. I can't dock a star from this book. It's that good. It's written by a mildly (but not offensively) dogmatic Danish guy who talks about sauces in every chapter. I like my Filets Mignons dry, thank you very much. And still, at the end of the day ... this is best software development book I have ever read. By far. By miles. By kilometers ...
34 von 35 Kunden fanden die folgende Rezension hilfreich
Must read for .NET Devs 18. November 2011
Von Art Gorr - Veröffentlicht auf Amazon.com
Format: Taschenbuch
I have never written a review for Amazon before but I want to take the time here to give major props to the author for this quality book on Dependency Injection. This is easily in the top 2 of software development books that I have read. (The other being R. Martin's Agile Principles, Patterns, and Practices in C#)

I have been using DI successfully for several years, yet I was able to learn an enormous amount about the topic from this book. Explanations of DI principles and related patterns such as Decorator really clicked for me. Read this book and you will understand how to develop loosely coupled software components. Excellent code examples in C#. The section on object composition in MS frameworks like ASP.NET MVC and WCF is an extremely valuable resource. The footnotes will direct you to very interesting reading for an even deeper dive. I could go on.

I highly recommend this book for .NET developers.
23 von 25 Kunden fanden die folgende Rezension hilfreich
Awesome, Awesome, Awesome, Awesome, Awesome... 4. Januar 2012
Von T. Anderson - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
Uhg. Sometimes my ability to be a complete ignoramus really annoys me. When I first saw this book on the upcoming list of books to be published I thought, "That sucks, I just got done reading Dependency Injection by Dhanji R. Prasanna last year. I don't need to read the .NET version", and so I ignored this book.

As time went on I saw all the great reviews coming out about the book and it made me curious. A buddy of mine had purchased it and I know that Manning gives ebooks with there book purchases, so I asked to borrow it. I ordered the book the next day.

I have nothing bad to say about Dependency Injection by Dhanji R. Prasanna, it was a great book. The difference is this one spoke my language of choice, .NET. It made the read so much better for me. Plus all the coverage of the popular DI Containers for .NET rocks.

This book is broken down into 4 parts the first part introduces DI. Part two is a catalog of patterns, anti-patterns, and refactorings. Part three covers Object Composition, Lifetime Management, and Interception. Part four covers all the popular DI .NET Containers which include Castle Windsor, StructureMap, Spring.NET, Autofac, Unity, and MEF.

One of the coolest things about the book is that it uses poor man's DI in the first 3 parts of the book to teach you how it all works, and then covers the popular DI .NET Containers in details to help you be more productive.

Coverage of the popular DI .NET Containers is nice deep coverage which also highlights the advantages and disadvantages of each one. Each popular DI .NET Container gets its own chapter. There are also some nice feature and lifestyle comparison charts to help you zero in on which DI Container will fit your needs.

The chapter on Object Composition is pretty cool too. It include coverage of console applications, ASP.NET MVC, Windows Communication Foundation, Windows Presentation Foundation, ASP.NET (Web Forms), and PowerShell.

The chapters on patterns and anti-patterns are a really big help in making sure you are using DI correctly. The patterns covered include Constructor Injection, Property Injection, Method Injection, and Ambient Context. The anti-patterns covered include Control Freak, Bastard Injection, Constrained Construction, and Service Locator. Both include nice code samples.

The chapter on DI refactoring covers mapping runtime value to abstractions, working with short-lived dependencies, resolving cyclic dependencies, dealing with constructor over-injection, and monitoring coupling.

This book is packed with diagrams that help you visualize the topic at hand. The author includes just the right amount.

Over all I found this author's writing style made the book a nice cover to cover read, but I will also be keeping it near to use as a reference. I have been on projects that use Castle Windsor, StructureMap, Unity, and MEF, so having coverage of each handy will be nice.

All the downloadable code is very well organized and usable.

This book is not only about DI, it is about proper object oriented programming. Every .NET architect and developer should read this book.
11 von 11 Kunden fanden die folgende Rezension hilfreich
Best Book in .NET best practices hands down 14. Dezember 2011
Von T. Stickel - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
I started in the 90's with VB and then VB.NET for .NET in 2001-2002. I made the transition to C# in 2002-2003 and I used the standard code behind model. I didn't know about DI / IOC / Unit Testing etc... until 3 years ago as I was using so many technologies. In the past few years of using MVC 1,2,3 and now doing unit testing , DI, design patterns, Mocking with Moq etc..., this book is vital for my development as a good developer. Mark Seemann writes so well. I now look best at the code I wrote 6 months ago as utter garbage. Knowing fundamental C# development is essential backbone to this book, but to skip on not owning and reading this book may possibly be the difference between having a job and not a having a job in .NET in 5 years. The .NET interviews I have had in the last 3-4 years have been increasingly demanding on what to know etc... This book fosters how to do things the right way. The manning books have also become a favorite, ... so move over Apress and Wrox ... Manning is king IMO. This book was recommended to me by a friend who worked for a Microsoft Gold Partner. Sometimes I go with Ebooks, but I'm glad I was the paperback of this one. Take your .NET to the next leavel. IOC and DI are NOT the same thing! The author is on stackoverflow.com answering questions etc... Even if you do Java or a Dynamic language, you will end up really thinking about software development that is loosely coupled for real, and not just a buzz word. Enjoy as I did.
6 von 6 Kunden fanden die folgende Rezension hilfreich
More than just Dependency Injection 8. April 2012
Von Dennis Rongo - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
My interest as of late has been in the area of Design Patterns and Architecture, and I've decided to give this book a go based on the excellent reviews that it has received so far.
This is one of those books in .NET that I wish I've read much sooner. The more I dig in deeper into the book's content, the more I wished that more books were written similar to this. The writing style is second to none (I can't stop reading), and DI is explained thoroughly.

The author initially goes back to the basics of DI and go over what it is and the problem that it tries to solves. He then proceeds to write code that are tightly coupled, which he then goes back and shows how it can be re-written or refactored to become loosely coupled. The book also covers DI containers or injectors as how it satisfies the need of resolving dependencies. Although DI containers are available, it's valuable to know what going on behind the scene and how to architect a project that is adaptable to any unforeseen scenarios.

There are technical books out there where authors gloss over a subject which means that they're either too lazy to explain it, or they're not knowledgeable enough in that area. This book is different. The author not just understand the subject but knows how to explain it very well. He covers all the grounds of Dependency Injection; the ins-and-outs as well as the finer details. There are no questions that are left unanswered. I was actually surprised how massive the book initially was and didn't think that covering DI would span into so many pages. I assumed a lot of things regarding DI and this book changed those assumptions as well as clarified a lot of things. I've gained not just knowledge in the scope of DI but as well as insights in Design Patterns. Reading this book made me re-evaluate my approach when architecting a new project or even how I approach an existing project's architecture.

I enjoyed reading this book and recommend this to all .NET developers of any level. Whatever you experience level is, you'll gain something from this book. It changed my thinking process on how I approach my code and have become a better developer overall. This is without a doubt a new favorite book of mine and I own tons of technical books already. I definitely had fun reading it and highly recommended.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.