Autres vendeurs sur Amazon
+ EUR 0,01 (livraison)
+ EUR 2,99 (livraison)
+ EUR 0,01 (livraison)
Continuous Integration in NET (Anglais) Broché – 24 mars 2011
|Neuf à partir de||Occasion à partir de|
- Choisissez parmi 17 000 points de collecte en France
- Les membres du programme Amazon Prime bénéficient de livraison gratuites illimitées
- Trouvez votre point de collecte et ajoutez-le à votre carnet d’adresses
- Sélectionnez cette adresse lors de votre commande
Les clients ayant acheté cet article ont également acheté
Description du produit
Présentation de l'éditeur
.NET Developers guide to the Continuous Integration software
engineering process, from theory to practice.
Continuous integration is a software engineering process designed to
minimize "integration hell." It's a coordinated development approach
that blends the best practices in software delivery. For .NET
developers, especially, adopting these new approaches and the tools
that support them can require rethinking the development process
Continuous Integration in .NET is a tutorial for developers and team
leads that teaches readers how to re-imagine their development
strategy by creating a consistent continuous integration process. This
book shows how to build on the tools they already know .NET
Framework and Visual Studio and to use powerful software like
MSBuild, Subversion, TFS 2010, Team City, CruiseControl.NET,
NUnit, and Selenium.
Practical and insightful guide.F
Covers concepts and tools.F
Aimed at .NET developers.
Biographie de l'auteur
runs a consultancy in Silesia, Poland. He has more
than 8 years experience in software development in fields ranging from
automotive to finance.
Craig Berntson, a 25-year veteran of the software industry, has been
Microsoft MVP since 1996 and speaks regularly throughout the US,
Canada, and Europe. He lives in Salt Lake City, UT.
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.
Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.
Détails sur le produit
Si vous vendez ce produit, souhaitez-vous suggérer des mises à jour par l'intermédiaire du support vendeur ?
|5 étoiles (0%)|
|4 étoiles (0%)|
|3 étoiles (0%)|
|2 étoiles (0%)|
|1 étoile (0%)|
Commentaires client les plus utiles sur Amazon.com
Not a very good story to start the review of a book on CI that I highly recommend you read. Times have changed, the tools have improved, and with books like this available you have no reason to not give CI a go. You may have plenty of excuses, but no reasons. Luckily this book contains a nice summary of excuses commonly used and does a nice job of debunking them.
The book starts off with a chapter titled Understanding continuous integration which gives a nice overview of CI and introduces the CI tools. They include source control, CI server, feedback mechanism, build manager, unit test framework, documenting, and code-analysis tools.
The book continues with chapters on Setting up a source control system, Automating the build process, Choosing the right CI server, Continuous feedback, Unit testing continuously integrated code, Performing integration, system, and acceptance testing, Analyzing the code, Generating documentation, Deployment and delivery, Continuous database integration, and Extending continuous integration.
One of the things I like about the book is that it is .NET centric and not Microsoft centric. It introduces the Microsoft tools, other vendor's tools, and open source tools. For example Subversion, TFS, SourceSafe, Git, and Vault are introduced as source control options, Nant and MSBuild are introduced as build tools, and CruiseControl.NET, TFS 2010, and TeamCity as CI servers.
The authors do a great job of providing in-depth examples of the different tools and technologies. The example's accompanying downloadable code is very well organized and usable.
Although implementing CI can be a big change for a team, this book will definitely help educate you and your team on all the different tools available in the context of .NET projects. That give a big advantage when planning your team's path to CI.
All in all I highly recommend using CI on your projects, but I recommend reading this book first even more.
That said, I would only recommend this book if you are at the "Where do I start?" stage with CI. I find myself referring to Stack Overflow when I have a CI-related problem instead of this book. It is not a reference. If you already have a general grasp of CI concepts you may want to consider a couple of in-depth books on specific topics instead of this one. If you already know what unit testing is, if you can edit a project file, if you know what FxCop is, then I would strongly consider a good book on MSBuild and deployment instead as that tends to cause the most head-scratchers.
This book is excellent to get you introduced in CI for .NET and to get started with a set of tools (not only from Microsoft) such as:
- CruiseControl.NET, TeamCity and Team Foundation Server (2010) as CI servers
- MS build as build automation tool
- NUnit, MS Test as unit testing framework
- PartCover as test coverage tool
- White, Selenium and FiNesse for integration, functional, acceptance tests
- FxCop (Code Analysis), NDepend for compiled code analysis
- StyleCop for source code analysis
- Sandcastle as documentation generation tool
- MS Setup, WiX and MS Deploy as setup / deployment tools
I read programming books on a Kindle app for iPad / iPhone rather than on a computer, so I appreciate that the book is easy to read, with handy screenshots that avoid you to install/use the tools on a computer to get the idea about them.
The book covers the basics of each area and tool, detailing some good and not so good things of each tool, and providing examples of use with a sample project. If you have decided that you are going to stick to free tools, you can skip some sections (and the same applies if you have decided to use only Microsoft tools).
But once you have decided which of the above area(s) of CI and tools you are going to use, likely you will need other books/docs to get deeper. For example, for unit testing I recommend "The Art of Unit Testing", also from Manning, but wait until the second edition is published. If you decide to use Team Foundation Server (TFS) version 2012, I recommend the free book "Testing for Continuous Delivery with Visual Studio 2012". For other tools, you will need to use the documentation of the product.
The book is also a good resource to get your team introduced to CI is that is your scenario. Many developers tend to be much more focused on the code / manual testing than on automated testing, let alone on continuous integration which maybe they ignore at all. Maybe with books like this they realize the spectrum of things that can be done automatically and in a continuous fashion.