EUR 64,75
  • Tous les prix incluent la TVA.
Habituellement expédié sous 4 à 6 semaines.
Expédié et vendu par Amazon. Emballage cadeau disponible.
Vous l'avez déjà ?
Repliez vers l'arrière Repliez vers l'avant
Ecoutez Lecture en cours... Interrompu   Vous écoutez un extrait de l'édition audio Audible
En savoir plus
Voir cette image

Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries (Anglais) Relié – 22 octobre 2008

5.0 étoiles sur 5 2 commentaires client

Voir les 2 formats et éditions Masquer les autres formats et éditions
Prix Amazon
Neuf à partir de Occasion à partir de
Format Kindle
"Veuillez réessayer"
Relié
"Veuillez réessayer"
EUR 64,75
EUR 64,75 EUR 67,05
Note: Cet article est éligible à la livraison en points de collecte. Détails
Récupérer votre colis où vous voulez quand vous voulez.
  • Choisissez parmi 17 000 points de collecte en France
  • Les membres du programme Amazon Premium bénéficient de livraison gratuites illimitées
Comment commander vers un point de collecte ?
  1. Trouvez votre point de collecte et ajoutez-le à votre carnet d’adresses
  2. Sélectionnez cette adresse lors de votre commande
Plus d’informations
click to open popover

Offres spéciales et liens associés


Descriptions du produit

Revue de presse

Framework Design Guidelines is one of those rare books that can be read at different reading levels and can be useful to different kinds of developers. Regardless of whether you want to design an effective object model, improve your understanding of the .NET Framework, borrow from the experience of software gurus, stay clear of the most common programming mistakes, or just get an idea of the huge effort that led to the .NET initiative, this book is a must-read.”

—Francesco Balena, The VB Migration Partner Team (www.vbmigration.com), Code Architect, Author, and Microsoft Regional Director, Italy

 

“Frameworks are valuable but notoriously difficult to construct: your every decision must be geared toward making them easy to be used correctly and difficult to be used incorrectly. This book takes you through a progression of recommendations that will eliminate many of those downstream ‘I wish I’d known that earlier’ moments. I wish I’d read it earlier.”

—Paul Besly, Principal Technologist, QA

 

“Not since Brooks’ The Mythical Man Month has the major software maker of its time produced a book so full of relevant advice for the modern software developer. This book has a permanent place on my bookshelf and I consult it frequently.”

—George Byrkit, Senior Software Engineer, Genomic Solutions

 

“Updated for the new language features of the .NET Framework 3.0 and 3.5, this book continues to be the definitive resource for .NET developers and architects who are designing class library frameworks. Some of the existing guidelines have been expanded with new annotations and more detail, and new guidance covering such features as extension methods and nullable types has also been included. The guidance will help any developer write clearer and more understandable code, while the annotations provide invaluable insight into some of the design decisions that made the .NET Framework what it is today.”

—Scott Dorman, Microsoft MVP and President, Tampa Bay International Association of Software Architects

 

“Filled with information useful to developers and architects of all levels, this book provides practical guidelines and expert background information to get behind the rules. Framework Design Guidelines takes the already published guidelines to a higher level, and it is needed to write applications that integrate well in the .NET area.”

—Cristof Falk, Software Engineer

 

“This book is an absolute must read for all .NET developers. It gives clear ‘do’ and ‘don’t’ guidance on how to design class libraries for .NET. It also offers insight into the design and creation of .NET that really helps developers understand the reasons why things are the way they are. This information will aid developers designing their own class libraries and will also allow them to take advantage of the .NET class library more effectively.”

—Jeffrey Richter, Author/Trainer/Consultant, Wintellect

 

“The second edition of Framework Design Guidelines gives you new, important insight into designing your own class libraries: Abrams and Cwalina frankly discuss the challenges of adding new features to shipping versions of their products with minimal impact on existing code. You’ll find great examples of how to create version N+1 of your software by learning how the .NET class library team

created versions 2.0, 3.0, and 3.5 of the .NET library. They were able to add generics, WCF, WPF, WF, and LINQ with minimal impact on the existing APIs, even providing capabilities for customers wanting to use only some of the new features, while still maintaining compatibility with the original library.”

—Bill Wagner, Founder and Consultant, SRT Solutions, author of Effective C# and More Effective C#

 

“This book is a must read for all architects and software developers thinking about frameworks. The book offers insight into some driving factors behind the design of the .NET Framework. It should be considered mandatory reading for anybody tasked with creating application frameworks.”

—Peter Winkler, Sr. Software Engineer, Balance Technology Inc.

 

“An instant classic.”

—From the Foreword by Miguel de Icaza

 

Présentation de l'éditeur

Framework Design Guidelines, Second Edition, teaches developers the best practices for designing reusable libraries for the Microsoft .NET Framework. Expanded and updated for .NET 3.5, this new edition focuses on the design issues that directly affect the programmability of a class library, specifically its publicly accessible APIs.

 

This book can improve the work of any .NET developer producing code that other developers will use. It includes copious annotations to the guidelines by thirty-five prominent architects and practitioners of the .NET Framework, providing a lively discussion of the reasons for the guidelines as well as examples of when to break those guidelines.

 

Microsoft architects Krzysztof Cwalina and Brad Abrams teach framework design from the top down. From their significant combined experience and deep insight, you will learn

  • The general philosophy and fundamental principles of framework design
  • Naming guidelines for the various parts of a framework
  • Guidelines for the design and extending of types and members of types
  • Issues affecting–and guidelines for ensuring–extensibility
  • How (and how not) to design exceptions
  • Guidelines for–and examples of–common framework design patterns

Guidelines in this book are presented in four major forms: Do, Consider, Avoid, and Do not. These directives help focus attention on practices that should always be used, those that should generally be used, those that should rarely be used, and those that should never be used. Every guideline includes a discussion of its applicability, and most include a code example to help illuminate the dialogue.

 

Framework Design Guidelines, Second Edition, is the only definitive source of best practices for managed code API development, direct from the architects themselves.

 

A companion DVD includes the Designing .NET Class Libraries video series, instructional presentations by the authors on design guidelines for developing classes and components that extend the .NET Framework. A sample API specification and other useful resources and tools are also included.

Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.

  • Apple
  • Android
  • Windows Phone
  • Android

Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.



Détails sur le produit

Commentaires en ligne

5.0 étoiles sur 5
5 étoiles
2
4 étoiles
0
3 étoiles
0
2 étoiles
0
1 étoile
0
Voir les deux commentaires client
Partagez votre opinion avec les autres clients

Meilleurs commentaires des clients

Par Sylvain Rodrigue TOP 100 COMMENTATEURSMEMBRE DU CLUB DES TESTEURS le 3 juin 2010
Format: Relié Achat vérifié
Framework Design Guidelines, dans ses deux versions (la secondes ajoutant peu à la première, mais elle vaut tout de même l'achat) est un livre vraiment exceptionnel que tous les amoureux du développement liront avec enthousiasme ! Il s'agit en quelque sorte des normes et des best practices qu'ont suivies les auteurs des diverses versions de .NET.

Ce qui est remarquable ici, c'est que chaque énoncé est suivi des commentaires de différents participants au framework .NET. Certains sont d'accord avec l'énoncé, d'autres le sont moins, et chacun expose son opinion dans un petit encadré.

Bien entendu, il n'existe pas de recette magique en informatique - la bonne pratique de l'architecte et du développeur d'à-coté peut être catastrophique sur d'autres projets. C'est hélas ce qu'oublient trop souvent les architectes et les développeurs, mais c'est surtout ce que rappellent sans cesse tout les petits encadrés suivant chaque préceptes établi par l'auteur...

Un modèle du genre, donc.

Mais ce qui m'aura le plus séduit dans ces livres, c'est l'orientation infiniment agile de ses auteurs (et ce, même si le mot "agile" n'est cité nulle part). L'intention des auteurs était de livrer le framework à la fois le plus complet et le moins envahissant possible. Bref, le framework le plus utilisable possible, ce qu'ils ont bien réussit à faire finalement.

Il est remarquable que très peu de design patterns aient été mis en oeuvre. Il y en a certes, mais il sont rares et aucune classe n'est suffixée du nom du pattern - un modèle je vous dis !
Lire la suite ›
Remarque sur ce commentaire 3 personnes ont trouvé cela utile. Avez-vous trouvé ce commentaire utile ? Oui Non Commentaire en cours d'envoi...
Merci pour votre commentaire.
Désolé, nous n'avons pas réussi à enregistrer votre vote. Veuillez réessayer
Signaler un abus
Format: Relié
Ce livre est une référence. Il dicte les bonnes pratiques de programmation sans tomber dans le "à faire quoiqu'il arrive".

Il y a trois types de conseils :
* faire
* ne pas faire
* pensez à

Cependant, même si l'auteur conseille parfois quelque chose, il laisse ensuite la parole à des développeurs d'exception en .Net pour qu'ils donnent leur point de vue. Bien souvent, ils apportent éclaircissements et nuances qui sont d'une valeur inestimable.

A mettre dans les mains de tous les développeurs.
Remarque sur ce commentaire Avez-vous trouvé ce commentaire utile ? Oui Non Commentaire en cours d'envoi...
Merci pour votre commentaire.
Désolé, nous n'avons pas réussi à enregistrer votre vote. Veuillez réessayer
Signaler un abus

Commentaires client les plus utiles sur Amazon.com (beta)

Amazon.com: 4.7 étoiles sur 5 22 commentaires
6 internautes sur 6 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 If you're going to write maintainable .NET code, get this book 5 décembre 2012
Par Dr. Curmudgeon - Publié sur Amazon.com
Format: Relié Achat vérifié
One of my all-time favorite programming books. Puts into very clear language practices that would have probably taken me a couple more years to come up to on my own.

It fully describes how and why the .NET framework is laid out the way it is, why the parts that seem to annoy you the most got it wrong and how, and provides many useful guidelines from helping you refrain from shooting yourself in the foot.

I might also say that it's equally applicable to just about any modern, sort of OO-based procedural language, but that would probably result in bloody religious wars.
2 internautes sur 2 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 excellent reference 17 novembre 2011
Par Paul Gehrman - Publié sur Amazon.com
Format: Relié Achat vérifié
This is an excellent book for .NET developers, although I wouldn't recommend it for beginners. I read it a few years ago when I first started in .NET and found it a bit overwhelming. However, after reading it again with a few more years of .NET under my belt, I found the book very informative and helpful in terms of understanding not only how public APIs should be built, but also excellent tidbits about various .NET coding best practices that are applicable to developing just about any type of app.

One other thing I'll mention about this book is that it is geared toward developing a public API, so many of the recommendations may not be applicable to your specific situation. Indeed, for the development of most apps that aren't going to be used by other developers, much simpler coding approaches and architectures can and should be used. Despite that, however, this book has a lot going for it and you'll certainly gain a much deeper understanding of .NET after reading it.
1 internautes sur 1 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Standing on the shoulders of giants 23 mai 2011
Par Peter Wone - Publié sur Amazon.com
Format: Relié Achat vérifié
Brimful of divine wit and wisdom, this book actually was written by the creators of a universe. In a departure from biblical tradition, it is comprehensive, internally consistent and rarely ambiguous. It is also surprisingly entertaining and engaging.

Known inconsistencies and ambiguities are called out and explained, sometimes apologetically, as the gods of dotnet expound principles and then explain their own acts of creation to illustrate best practice - or sometimes worst practice, when they failed to heed their own advice. The text is littered with inset comments, as though the authors were standing around reviewing a draught of the book with you. They don't always share opinions, and the voice of dissent is as instructive as the explications.

I bought the first edition and loved it, giving it into the hands of someone who needed it. Now I have the second edition. Every now and then I skim it just to refresh my understanding, and sometimes to glean new insight in the context of more experience. Few of us will ever write an application framework, yet I think all of us would be better programmers if we shared the wisdom of those who do. Buy the book. If nothing else it's a hell of a conversation piece.
5.0 étoiles sur 5 Essential read for all .NET developers 23 octobre 2011
Par Bill Sorensen - Publié sur Amazon.com
Format: Relié Achat vérifié
I've bought this book three times: the first edition, the second edition, and the Kindle edition (for searching).

The authors don't just give you guidelines; they give you the reasons behind the guidelines. These reasons are ones learned at Microsoft during the development of the .NET Framework. They tell you what worked and what didn't.

You get multiple points of view, sometimes dissenting. There are, by my count, 25 reviewers / annotators, including Anders Hejlsberg.

The chapter on Common Design Patterns is one I reference frequently.

There are other gems in here, such as Appendix C: Sample API Specification:

"APIs that were designed by writing code samples before actually designing the API are generally successful. APIs that were designed before code samples were written to show how the resulting APIs should be used are often too complex, not self-explanatory, and ultimately need to be fixed in subsequent releases."

If your first instinct upon being told "do it this way" is to ask "why?", this is the book for you.
4.0 étoiles sur 5 A little dry but informative 16 avril 2010
Par Dennis Rongo - Publié sur Amazon.com
Format: Relié Achat vérifié
I would only recommend this book if you're an intermediate or advanced .NET developer as there's a lot of high-level concepts discussed. Understanding the premises of object oriented programming is important as the book will talk about various techniques revolving this main concept. The book does feel very much like a textbook and can be dry but nonetheless, you'll pick up a thing or two that will make you a better programmer. I found the random comments throughout the book to be a good supplemental feature to the topic being discussed as some are key personalities in the industry; and it's always good what they have to say.

Lastly, the included DVD is just a presentation that can be found easily online, so it's nothing to be excited about. If you're looking to become a better API designer, or a better programmer, the book is a must-have. On the other hand, if you're a novice, you'd want to maybe hold off buying until you've understand the basics of OO and programming in general.
Ces commentaires ont-ils été utiles ? Dites-le-nous

Rechercher des articles similaires par rubrique


Commentaires

Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?