Making Sense of Partial Classes
Publish Date: Oct. 4, 2004
In Whidbey, Microsoft has introduced partial classes, with which we can spread the definition of a class over multiple files. The use of partial classes attempts to solve the problem of separation of designer code and implementation code. Nick Harrison shows you these solutions and explores the benefits of using partial classes in your own projects.
Understanding Reflection, Part 2
Publish Date: Nov. 17, 2003
In the first article of this series, Nick Harrison explored some of the basic objects used to make reflection work. In this second part, he shows you how to use custom attributes to define and reference metadata that the original .NET designers never imagined.
Understanding Reflection, Part 1
Publish Date: Oct. 6, 2003
Sometimes it is useful to be able to examine information about the objects in your applications. In this article, Nick Harrison starts you out with the basics of reflection.
Understanding Interfaces in .NET
Publish Date: Jun. 30, 2003
.NET introduces the potentially confusing concept of an interface. An interface is a contract that defines the signature of some piece of functionality. Throughout the .NET framework, interfaces are used to define that certain types have well-known behaviors. Nick Harrison explains what interfaces are and how to use them in your own classes.
Using the CodeDOM
Publish Date: Feb. 3, 2003
One of the promises of .NET is that the language used is secondary to the framework. The classes in the CodeDom namespace really drive this point home. Using CodeDom, we build a tree, or graph, populated with objects from the System.CodeDom namespace, and after the tree is populated, we use the CodeProvider object provided by every .NET language to convert the tree into code in that language. This makes switching languages as simple as switching the CodeProvider used at the end. In this article, Nick Harrison shows you the ins and outs of using the CodeDOM.
Transparent Database Access with ADO.NET
Publish Date: Dec. 16, 2002
The dream of transparent data access is to not have to care about where the data is coming from; you have more important things to worry about, like providing a nice user interface and getting the business logic right on time. Ideally, it should not matter whether the data is coming from SQL Server, Oracle, Outlook, or anywhere else useful data may be stored. This article by Nick Harrison explains how to achieve this nirvana in .NET.
© 2013, O’Reilly Media, Inc.
All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners.