Chapter 4 of Framework Design Guidelines, titled "Type Design Guidelines," presents guidelines that describe when and how to design classes, structs and interfaces. In this chapter, the authors divide types into four groups and discuss the do's and don'ts of type design.
In the past couple of years, unit testing has gained tremendously in popularity; but while most developers understand the overall concept, certain aspects have been more elusive. Among these is how to effectively replace component servers for testing purposes. Most people call these replacements stubs or mocks, but as I will show in this article, these are only two types in a larger continuum of replacements.
Web Services are an integral part of the .NET framework that provide a cross-platform solution for exchanging data between distributed systems. Although Web Services are normally used to allow different operating systems, object models and programming languages to send and receive data, they can also be used to dynamically inject data into an ASP.NET AJAX page or send data from a page to a back-end system. All of this can be done without resorting to postback operations.
This article examines how the new support for functional programming techniques in .NET 3.5 can developers make code more declarative, reduce errors in code, and write fewer lines of code for many common tasks.
Recursion can be a powerful programming technique when used wisely. Some data structures such as tree structures lend themselves far more easily to manipulation by recursive techniques. As it is also a classic Computer Science problem, it is often used in technical interviews to probe a candidate's grounding in basic programming techniques.
This article covers the subject of software testing mocks (also known as test doubles, stubs and fakes, amongst other names). It compares also the creation manual mocks with the usage of a full-fledged mocking framework. The article also gives examples in the .NET context.
This tutorial explores the principles of parameterized unit testing with Microsoft Pex 2010, which is a Microsoft® Visual Studio® add-in that provides a runtime code analysis tool for .NET Framework code.