|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
Wird oft zusammen gekauft
Produktinformation
|
Mehr über den Autor
Entdecken Sie Bücher, lesen Sie über Autoren und mehr
› Besuchen Sie die Seite von Mark Seemann auf Amazon
› Besuchen Sie die Seite von Mark Seemann auf Amazon
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
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis | Rückseite
Vorgeschlagene Tags zu ähnlichen Produkten(Was ist das?)Setzen Sie den ersten relevanten Tag hinzu (ein Schlüsselwort, das mit diesem Produkt in engem Zusammenhang steht).
|
Eine digitale Version dieses Buchs im Kindle-Shop verkaufen
Wenn Sie ein Verleger oder Autor sind und die digitalen Rechte an einem Buch haben, können Sie die digitale Version des Buchs in unserem Kindle-Shop verkaufen.
Weitere Informationen
Kundenrezensionen
Die hilfreichsten Kundenrezensionen
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.
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.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
17 Rezensionen
13 von 13 Kunden fanden die folgende Rezension hilfreich
Must read for .NET Devs
18. November 2011
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.
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.
8 von 8 Kunden fanden die folgende Rezension hilfreich
Awesome, Awesome, Awesome, Awesome, Awesome...
4. Januar 2012
Format:Taschenbuch|Von Amazon bestätigter 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.
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.
4 von 4 Kunden fanden die folgende Rezension hilfreich
Best Book in .NET best practices hands down
14. Dezember 2011
Format:Taschenbuch|Von Amazon bestätigter 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.
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
|
|
Ähnliche Artikel finden
Anhand des Sachgebietes nach ähnlichen Produkten suchen:
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
