Test-Driven Development in Microsoft .NET
Learn how to apply the concepts and techniques of Test-Driven Development (TDD) to writing software for Microsoft .NET. Two experts in agile software development teach#151;using a wealth of pragmatic examples in C# and other .NET development tools#151;how to use automated tests to drive lean, efficient coding and better design. You'll focus on .NET-specific issues for TDD, including the best time to employ the inherent features of .NET class libraries and how to use NUnit, a leading unit-testing framework for .NET. And you'll see real-world examples of TDD-for .NET projects, including a Microsoft ADO.NET relational database, a user interface created with Microsoft ASP.NET and Microsoft Windows- Forms, Web services, and other useful applications.


The authors have been working with Remote Installation Services since its birth in 1999. We are really enthusiastic about working with it. From their experiences from very different customers with very different requirements to their Windows infrastructure environment, they have gained a tremendous deal of experience and in-depth knowledge with Remote Installation Services that other people can benefit from. This includes basic understanding, a lot of theory and best-practices, but also how you can stretch Remote Installation Services to really do what any system or network administrator would require. This information is essential for anyone wishing to implement Remote Installation Services and use the advanced features and tools it contains. There is much more than up grades, adding and deleting programs from a central administrator that can be done In addition it can save the cost adding a costly third party software package like Alteris to the enterprise network. This is the reason that the authors are now gathering all the experience and knowledge, and focusing on forming a single point of entry to everything you must know about Remote Installation Services in form of a book.


The Microsoft .NET Framework is exactly what its name implies: A general system onto which a lot of application-specific technologies are stuck. Essential ASP.NET With Examples in C# assumes you know something about the .NET way of doing things, and want to know more about how you can use its ASP.NET facet to implement robust and stylish Web applications. Fritz Onion, in a manner typical of this series, introduces key ASP.NET concepts logically, and with lots of code listings that make it clear how the concepts should be translated into reality. The truth be told, Onion excels at combining conceptual information with practical examples. This is unusual among writers of technical books, who tend to be good at (at best) one or the other.
Learn how to improve your C# coding skills using unit testing. Despite it's name, unit testing is really a coding technique, not a testing technique. Unit testing is done by programmers, for programmers. It's primarily for our benefit: we get improved confidence in our code, better ability to make deadlines, less time spent in the debugger, and less time beating on the code to make it work correctly. This book shows how to write tests, but more importantly, it goes where other books fear to tread and gives you concrete advice and examples of what to test–the common things that go wrong in all of our programs. Discover the tricky hiding places where bugs breed, and how to catch them using the freely available NUnit framework. It's easy to learn how to think of all the things in your code that are likely to break. We'll show you how with helpful mnemonics, summarized in a handy tip sheet. With this book you will: write better code, and take less time to write it; discover the tricky places where bugs breed; learn how to think of all the things that could go wrong; test individual pieces of code without having to include the whole project; and test effectively with the whole team. We'll also cover how to use Mock Objects for testing, how to write high quality test code, and how to use unit testing to improve your design skills. We'll show you frequent "gotchas" - along with the fixes - to save you time when problems come up. But the best part is that you don't need a sweeping mandate to change your whole team or your whole company. You don't need to adopt Extreme Programming, or Test-Driven Development, or change your development process in order to reap the proven benefits of unit testing. You can start unit testing, the pragmatic way, right away. 












