Use of Factory Method Design Pattern in the .NET Framework
Published in O'Reilly ONDotNet.com, August 2003. Republished by MSDN Academic Alliance, August 2003
Many popular software libraries make extensive use of design patterns so that the APIs can be abstracted out at a high level for the end programmer. The .NET Framework Class Library (FCL) is no exception. Given that the FCL builds on the strengths of Microsoft's experience with developing software libraries, one can assume that instances of design patterns found in the FCL are fairly appropriate usages of these patterns. This article describes some instances of a commonly occurring design pattern in the FCL: the Factory Method design pattern.

Team Development with Visual Studio .NET on a Shared Server
Published in .NET Developer's Journal, June 2003
Anyone who has created a Web project with Visual Studio .NET 2002 is aware that VS.NET ties the location of the Web project to a virtual directory on IIS, making it impossible for multiple Web projects to share session state. This article offers: (1) the ability to create multi-project Web applications using VS.NET while sharing the same IIS virtual root, hence sharing the same session state; and (2) the ability to support multiple developers using VS.NET for developing Web applications on the same server.

Create Richer Hyperlinks with JSP Custom Tags
Published in O'Reilly ONJava.com, April 2003
Gone are the days where one destination per link was enough. With mirroring, localization, and internationalization, your readers might want the choice of several different resources for any given link. Until XLink and XPointer are well supported in browsers and authoring tools, most alternatives are clumsy. This article demonstrates a better approach by creating a custom JSP tag to control a dynamic menu of destination links.

Manage Users with JMS
Published in JavaWorld, March 2003
Many enterprises have a federated set of homegrown and purchased applications that store their own copies of user contact information. In this age of mergers and acquisitions, a company's multiple business units or departments often carry redundant user information. Although most applications only store information about a specific application's users, the same user information is frequently stored in multiple applications. To maintain consistency and avoid customer confusion, these copies need to be synchronized regularly, and can be a challenge to maintain. This article describes a simple solution to this common problem of maintaining consistent user information across various business applications.

Writing Type-Safe Collections in C#
Published in O'Reilly ONDotNet.com, March 2003. Republished by MSDN Academic Alliance, March 2003
Statically typed programming languages allow earlier error checking, better enforcement of programming styles, and generation of more efficient object code than languages where all type consistency checks are performed at run time. However, even in statically typed languages, there is often the need to deal with data whose type cannot be determined at compile time. This is especially true for the .NET collections framework. This article describes three ways in which you can create compile-time checked collections in C#.