Reposted from Brother Kun’s blog http://www.jackspace.cn Microsoft.CSharp Contains classes that support compilation and code generation using the C# language. Microsoft.JScript Contains classes that support compilation and code generation using the JScript language. Microsoft.VisualBasic Contains classes that support compilation and code generation using the Visual Basic .NET language. Microsoft.Vsa Contains interfaces that let you integrate scripting engines of the .NET Framework into your application and compile and execute code at runtime. Microsoft.Win32 Provides two types of classes: classes that handle events raised by the operating system, and classes that operate on the system registry. System Contains base classes and base types that are used to define commonly used values and reference data types, events and event handlers, interfaces, attributes, and to handle exceptions. Other classes provide services that support the following operations: data type conversion, method parameter manipulation, mathematical computation, remote and local procedure calls, application environment management, and supervision of managed and unmanaged applications. System.CodeDom Contains classes that can be used to represent the elements and structure of source code documents. These elements can be used to build the structure of source code documents. Using the functionality provided by the System.CodeDom.Compiler namespace, you can output source code documents as source code written in a supported language. System.CodeDom.Compiler Contains types used to manage the generation and compilation of source code in supported programming languages. Each code generator can generate source code in a specific programming language based on the structure of the CodeDOM (Code Document Object Model) source model, composed of the elements provided by the System.CodeDom namespace. System.Collections Contains interfaces and classes that define various collections of objects, such as lists, queues, bit arrays, hash tables, and dictionaries. System.Collections.Specialized Contains specialized, strongly-typed collections; for example, linked-list dictionaries, bit vectors, and collections containing only strings. System.ComponentModel Provides classes used to implement the runtime and design-time behavior of components and controls. This namespace includes base classes and interfaces for property and type converter implementations, data source binding, and component licensing. System.ComponentModel.Design Contains classes that developers can use to build custom design-time component behaviors and user interfaces that configure components at design time. The design-time environment provides a system that lets developers arrange components and configure their properties. System.ComponentModel.Design.Serialization Provides types that support customizing and controlling serialization at design time. System.Configuration Provides classes and interfaces that let you programmatically access .NET Framework configuration settings and handle errors in configuration files (.config files). System.Configuration.Assemblies Contains classes used to configure assemblies. System.Configuration.Install Provides classes that let you write custom installers for your components. The Installer class is the base class for all custom installers in the .NET Framework. System.Data Consists essentially of the classes that make up the ADO.NET structure. The ADO.NET structure lets you build components that can be used to efficiently manage data from multiple data sources. In disconnected scenarios (such as the Internet), ADO.NET provides tools to request, update, and reconcile data in a multi-tier system. The ADO.NET structure can also be implemented in client applications (such as Windows Forms) or HTML pages created by ASP.NET. System.Data.Common Contains classes shared by .NET Framework data providers. A .NET Framework data provider describes a collection of classes used to access a data source (such as a database) in managed space. System.Data.Odbc Encapsulates the ODBC .NET Framework data provider. A .NET Framework data provider describes a collection of classes used to access a data source (such as a database) in managed space. Using the OdbcDataAdapter class, you can fill a DataSet that resides in memory, which you can use to query and update the data source. For additional information on how to use this namespace, see the OdbcDataReader, OdbcCommand, and OdbcConnection classes. Note: this namespace is only supported in version 1.1 of the .NET Framework. System.Data.OleDb Encapsulates the OLE DB .NET Framework data provider. The OLE DB .NET Framework data provider describes…
Note: this namespace is only supported in version 1.1 of the .NET Framework.
System.Data.SqlTypes Provides classes for the native data types in SQL Server. These classes provide a safer, faster alternative to other data types. Using the classes in this namespace helps prevent type-conversion errors that can occur in situations where precision may be lost. Because other data types convert to and from SqlTypes behind the scenes, explicitly creating and using objects within this namespace also produces faster code. System.Diagnostics Provides classes that allow interaction with system processes, event logs, and performance counters. This namespace also provides classes that let you debug applications and trace code execution. For more information, see the Trace and Debug classes. System.Diagnostics.SymbolStore Provides classes that let you read and write debug symbol information (such as the source line mapped to Microsoft Intermediate Language (MSIL)). Compilers targeting the .NET Framework can store debug symbol information in a programmer’s database (PDB) file. Debuggers and code analysis tools can read the debug symbol information at runtime. System.DirectoryServices Provides easy access to Active Directory from managed code. This namespace contains two component classes: DirectoryEntry and DirectorySearcher. These two classes use Active Directory Service Interfaces (ADSI) technology. ADSI is a set of interfaces provided by Microsoft, a tool that flexibly handles various network providers. ADSI lets administrators relatively easily find and manage network resources, regardless of network size. System.Drawing Provides access to the basic graphics functionality of GDI+. The System.Drawing.Drawing2D, System.Drawing.Imaging, and System.Drawing.Text namespaces provide more advanced functionality. System.Drawing.Design contains classes that extend the design-time user interface (UI) logic and drawing. This design-time functionality can be further extended to create the following objects: custom toolbox items, type-specific value editors or type converters, where the type-specific value editor is used to edit and graphically represent the values of the supported types; type converters are used to convert values between specific types. This namespace provides the basic framework for developing design-time UI extensions. System.Drawing.Drawing2D Provides advanced 2D and vector graphics functionality. This namespace includes gradient brushes, the Matrix class (used to define geometric transformations), and the GraphicsPath class. System.Drawing.Imaging Provides advanced GDI+ image processing functionality. The basic graphics functionality is provided by the System.Drawing namespace. System.Drawing.Printing Provides services related to printing. Typically, you create an instance of the PrintDocument class, set the properties that describe the printed content, then call the Print method to actually print the document. System.Drawing.Text provides advanced GDI+ typography functionality. The basic graphics functionality is provided by the System.Drawing namespace. The classes in this namespace let users create and use font collections. System.EnterpriseServices Provides important infrastructure for enterprise-level applications. COM+ provides the service structure for the component programming model deployed in enterprise environments. This namespace provides .NET Framework objects access to COM+ services, making .NET Framework objects more suitable for enterprise-level applications. System.EnterpriseServices.CompensatingResourceManager Provides classes that let you use the Compensating Resource Manager (CRM) in managed code. CRM is a service provided by COM+ that lets you include non-transactional objects in a Microsoft Distributed Transaction Coordinator (DTC) transaction. Although CRM does not provide the functionality of a full resource manager, they do provide transactional atomicity (all-or-nothing behavior) and durability through a recovery log. System.EnterpriseServices.Internal Provides infrastructure support for COM+ services. The classes and interfaces in this namespace are specifically designed to support calls from unmanaged COM+ classes into System.EnterpriseServices. System.Globalization Contains classes that define culture-related information, including language, country/region, calendar in use, date format patterns, currency, numbers, and string sort order. These classes are useful for writing globalized (internationalized) applications. System.IO Contains types that allow synchronous and asynchronous reading and writing of data streams and files. System.IO.IsolatedStorage Contains types that allow the creation and use of isolated storage areas…
System.Messaging Provides classes that let you connect to, monitor, and manage message queues on the network, and send, receive, or view messages. System.Net Provides a simple programming interface for the many protocols currently used by the network. The WebRequest and WebResponse classes form the basis of the so-called pluggable protocols, an implementation of a network service that lets you develop applications that use Internet resources without considering the specifics of each protocol. System.Net.Sockets Provides a managed implementation of the Windows Sockets (Winsock) interface for developers who need tight control over network access. System.Reflection Contains classes and interfaces that provide a managed view of loaded types, methods, and fields, and the ability to dynamically create and invoke types. System.Reflection.Emit Contains classes that allow compilers or tools to emit metadata and Microsoft Intermediate Language (MSIL) and optionally generate PE files on disk. The main clients of these classes are script engines and compilers. System.Resources Provides classes and interfaces that let developers create, store, and manage the various culture-specific resources used in an application. System.Runtime.CompilerServices Provides functionality for compiler writers using managed code to specify attributes in metadata that affect the runtime behavior of the common language runtime. The classes in this namespace are for compiler writers only. System.Runtime.InteropServices Provides members that support COM Interop and platform invoke services. If you are unfamiliar with these services, see Interoperating with Unmanaged Code. System.Runtime.InteropServices.CustomMarshalers Supports the .NET infrastructure and is not used directly in code. System.Runtime.InteropServices.Expando Contains the IExpando interface, which allows modifying an object by adding or removing its members. System.Runtime.Remoting Provides classes and interfaces that let developers create and configure distributed applications. System.Runtime.Remoting.Activation Provides classes and objects that support server- and client-side remote object activation. System.Runtime.Remoting.Channels Contains classes that support and process channels and channel sinks, which serve as the transport medium when clients call methods on remote objects. System.Runtime.Remoting.Channels.Http Contains channels that use the HTTP protocol to transport messages and objects between remote locations. By default, the HTTP channel encodes object and method calls in SOAP format for transmission, but other encoding and decoding formatter sinks can be specified in the channel’s configuration properties. System.Runtime.Remoting.Channels.Tcp Contains channels that use the TCP protocol to transport messages and objects between remote locations. By default, the TCP channel encodes object and method calls in binary format for transmission, but other encoding and decoding formatter sinks can be specified in the channel’s configuration properties. System.Runtime.Remoting.Contexts Contains objects that define the context in which all objects reside. A context is an ordered sequence of properties that define the environment in which the objects within it reside. A context is created during the activation of an object, and these objects are configured to require certain automatic services, such as synchronization, transactions, just-in-time (JIT) activation, security, etc. Multiple objects can reside in one context. System.Runtime.Remoting.Lifetime Contains classes that manage the lifetime of remote objects. Traditionally, distributed garbage collection uses reference counting and pinging to control object lifetime. This mechanism works fine when each service has few clients, but not when each service has thousands of clients. The remoting lifetime service associates each service with a lease, and when the lease expires, the service is removed. The lifetime service can act as a traditional distributed garbage collector and also adjusts well as the number of clients per service increases. System.Runtime.Remoting.Messaging Contains classes used to create and process remoting messages. The remoting infrastructure uses messages to communicate with remote objects. Messages are used to transmit remote method calls, activate remote objects, and exchange information. A message object carries a set of named properties, including an operation identifier, delegate information, and parameters. System.Runtime.Remoting.Metadata Contains classes and attributes that can be used to customize the generation and processing of SOAP for objects and fields. The classes in this namespace can be used to indicate SOAPAction, type output, XML element names, and XML namespace URI methods. **System.Runtime.R…
System.Web.Services.Configuration Consists of classes that configure how XML Web services created with ASP.NET run. System.Web.Services.Description Consists of classes that let you use the Web Services Description Language (WSDL) to publicly describe XML Web services. Each class in this namespace corresponds to a specific element in the WSDL specification, and the class hierarchy corresponds to the XML structure of a valid WSDL document. System.Web.Services.Discovery Consists of classes that let XML Web service clients locate XML Web services available on a Web server through a process called “XML Web service discovery.” System.Web.Services.Protocols Consists of classes that define the protocols used to transmit data over the network between XML Web service clients and XML Web services created with ASP.NET during communication. System.Web.SessionState Provides classes and interfaces that support storing data specific to an individual client in a Web application on the server. Session state data is used to give the client the appearance of a persistent connection to the application. State information can be stored in local process memory, or, for web farm configurations, can be stored out of process using the ASP.NET state service or a SQL Server database. System.Web.UI Provides classes and interfaces that let you create controls and pages that appear in a Web application as a user interface on a Web page. This namespace includes the Control class, which provides a common set of functionality for all controls (whether HTML controls, Web controls, or user controls). It also includes the Page control, which is automatically generated whenever a request is made to a page in a Web application. It also provides classes that offer Web Forms server control data binding functionality, the ability to save the view state of a given control or page, and parsing functionality applicable to both programmable and literal controls. System.Web.UI.Design Contains classes that can be used to extend Web Forms design-time support. System.Web.UI.Design.WebControls Contains classes that can be used to extend Web server control design-time support. System.Web.UI.HtmlControls Contains a collection of classes that let you create HTML server controls on a Web Forms page. HTML server controls run on the server and map directly to the standard HTML tags supported by most browsers. This lets you programmatically control the HTML elements on a Web Forms page. System.Web.UI.MobileControls Contains a set of ASP.NET server controls that can intelligently render your application for different mobile devices. System.Web.UI.MobileControls.Adapters Contains the core device adapter classes used by ASP.NET mobile controls to customize devices and support extending devices. System.Web.UI.WebControls Contains classes that let you create Web server controls on a Web page. Web server controls run on the server and include form controls such as buttons and text boxes. They also include special controls like a calendar. Because Web server controls run on the server, you can programmatically control these elements. Web server controls are more abstract than HTML server controls. Their object model does not necessarily reflect HTML syntax. System.Windows.Forms Contains classes used to create Windows-based applications that can take full advantage of the rich user interface functionality in the Microsoft Windows operating system. System.Windows.Forms.Design Contains classes that support the design-time configuration and behavior of Windows Forms components. These classes include: designer classes that provide Windows Forms component (a set of design-time services) support, UITypeEditor classes used to configure specific property types, and classes used to import ActiveX controls. System.Xml Provides standards-based XML processing support. System.Xml.Schema Contains XML classes that provide standards-based XML Schema Definition Language (XSD) schema support. System.Xml.Serialization Contains classes used to serialize objects into XML-format documents or streams. System.Xml.XPath Contains the XPath parser and evaluation engine. It supports the W3C XML Path Language (XPath) version 1.0 recommendation (www.w3.org/TR/xpat…