Design Guidelines Update: Exposing XML Data

Small update to the Design Guidelines courtesy of the XML team. System.Xml Usage Exposing XML Data  Do provide overloads that accept and System.Xml.XmlReader and System.String for properties of a class that represent an XML document or fragment. This gives users a friendly way to access the XML by using String and an efficient way to…

10

Design Guidelines Update: Resources

We just added some new design guidelines related to naming and usage of resources. Enjoy. Resources Resources can be used in libraries to store error messages, labels, and icons. MSDN article Resources and Localization Using the .NET Framework SDK is a good source of background information on the .NET Framework resource model. There are two…

14

Why Design Guidelines?

Many assume that the Design Guidelines document is intended to be a repository of the best solutions to common API design problems. Let me get it straight right away. This is not the intention at all. The main purpose of the Design Guidelines is to achieve consistency in reusable library APIs.   In a lot…

4

Design Guidelines Update: Generics

Generics is a new feature added to the Whidbey CLR and languages. We are still learning the best way to take advantage of the feature in reusable library APIs. The guidelines below represent out current thinking in this area. 1.0 Generics A new feature in CLR that allows classes, structures, interfaces, and methods to be…

66

Design Guidelines Category

The .NET Framework documentation on MSDN has a section describing the design guidelines for managed library developers. The section is based on an internal document that I help to create and maintain. The internal document is being constantly and frequently updated – much more frequently than the MSDN documentation. I started this blog with the…

2