Master Overview

The System.Web.UI namespace provides classes and interfaces that enable you to create ASP.NET server controls and ASP.NET Web pages for the user interface of your ASP.NET Web applications.

Microsoft.Build.BuildEngine

The Microsoft.Build.BuildEngine namespace represents the MSBuild engine. For information, see MSBuild.

Microsoft.Build.Framework

The Microsoft.Build.Framework namespace contains the types that define how tasks and loggers interact with the vstecmsbuild engine. For information, see MSBuild.

Microsoft.Build.Utilities

The Microsoft.Build.Utilities namespace provides helper classes that you can use to create your own MSBuild loggers and tasks. For information, see MSBuild.

Microsoft.CSharp

The Microsoft.CSharp namespace contains classes that support compilation and code generation using the C# language.

Microsoft.SqlServer.Server

The Microsoft.SqlServer.Server namespace contains classes, interfaces, and enumerations that are specific to the integration of the Microsoft .NET Framework common language runtime (CLR) into Microsoft SQL Server, and the SQL Server database engine process execution environment.

Microsoft.VisualBasic

The Microsoft.VisualBasic namespace contains types that support the vbprvb Runtime in vbprvb.

Microsoft.Win32



The Microsoft.Win32.SafeHandles namespace contains classes that are abstract derivations of safe handle classes that provide common functionality supporting file and operating system handles.

Microsoft.Win32

The Microsoft.Win32 namespace provides two types of classes: those that handle events raised by the operating system and those that manipulate the system registry.



The Microsoft.Win32.SafeHandles namespace contains classes that are abstract derivations of safe handle classes that provide common functionality supporting file and operating system handles.

Mono.CodeGeneration

Mono.Security.Protocol.Ntlm

Mono.Security.Protocol.Tls

System

The System namespace contains the fundamental types of the runtime, including the Object, Int32, and String types.

System

System

System

The System namespace contains fundamental classes and base classes that define commonly-used value and reference data types, events and event handlers, interfaces, attributes, and processing exceptions.

System.CodeDom

The System.CodeDom namespace contains classes that can be used to represent the elements and structure of a source code document. The classes in this namespace can be used to model the structure of a source code document that can be output as source code in a supported language using the functionality provided by the System.CodeDom.Compiler namespace.


The System.CodeDom.Compiler namespace contains types for managing the generation and compilation of source code in supported programming languages. Code generators can each produce source code in a particular programming language based on the structure of Code Document Object Model (CodeDOM) source code models consisting of elements provided by the System.CodeDom namespace.

System.Collections

The System.Collections namespace contains interfaces and classes that define various collections of objects, such as lists, queues, bit arrays, hash tables and dictionaries.







The System.Collections.Concurrent namespace provides several thread-safe collection classes that should be used in place of the corresponding types in the System.Collections and System.Collections.Generic namespaces whenever multiple threads are accessing the collection concurrently.


The System.Collections.Generic namespace contains interfaces and classes that define generic collections, which allow users to create strongly typed collections that provide better type safety and performance than non-generic strongly typed collections.


The System.Collections.ObjectModel namespace contains classes that can be used as collections in the object model of a reusable library. Use these classes when properties or methods return collections.


The System.Collections.Specialized namespace contains specialized and strongly-typed collections; for example, a linked list dictionary, a bit vector, and collections that contain only strings.

System.ComponentModel

The System.ComponentModel namespace provides classes that are used to implement the run-time and design-time behavior of components and controls. This namespace includes the base classes and interfaces for implementing attributes and type converters, binding to data sources, and licensing components.


The System.ComponentModel.Design.Data namespace contains classes you can use to build custom design-time behavior for data-related components.




The System.ComponentModel.Design.Serialization namespace provides types that support customization and control of serialization at design time.


The System.ComponentModel.Design namespace contains classes that developers can use to build custom design-time behavior for components and user interfaces for configuring components at design time. The design time environment provides systems that enable developers to arrange components and configure their properties. Some components may require specific design-time only behavior to function properly in a design time environment. It may also be valuable to provide custom user interfaces which assist developers in configuring components or the values of complex data types. The classes and interfaces defined within this namespace can be used to build design-time behavior for components, access design-time services, and implement customized design-time configuration interfaces.

System.Configuration

The System.Configuration namespace contains the types that provide the programming model for handling configuration data.


The System.Configuration.Assemblies namespace contains classes that are used to configure an assembly.


The System.Configuration.Install namespace provides classes that allow you to write custom installers for your own components. The Installer class is the base class for all custom installers in the.NET Framework.

System.Data

The System.Data namespace provides access to classes that represent the ADO.NET architecture. ADO.NET lets you build components that efficiently manage data from multiple data sources.


The System.Data.Common namespace contains classes shared by the .NET Framework data providers.


The System.Data.Odbc namespace is the .NET Framework Data Provider for ODBC.


The System.Data.OleDb namespace is the.NET Framework Data Provider for OLE DB.


The System.Data.Sql namespace contains classes that support SQL Server-specific functionality.


The System.Data.SqlClient namespace is the.NET Framework Data Provider for SQL Server.


The System.Data.SqlTypes namespace provides classes for native data types in ssNoVersion. These classes provide a safer, faster alternative to the data types provided by the .NET Framework common language runtime (CLR). Using the classes in this namespace helps prevent type conversion errors caused by loss of precision. Because other data types are converted to and from SqlTypes behind the scenes, explicitly creating and using objects within this namespace also yields faster code.


The System.Data.Design namespace contains classes that can be used to generate a custom typed-dataset.

System.Deployment.Internal

The System.Deployment.Internal namespace contains helper classes for accessing the internal members of ActivationContext and ApplicationIdentity objects.

System.Diagnostics

This namespace contains classes for interacting with system resources like event logs, processes, and performance counters.


The System.Diagnostics.Contracts.Internal namespace provides classes that the binary rewriter can use to handle a contract failure.


The System.Diagnostics.Contracts namespace contains static classes for representing program contracts such as preconditions, postconditions, and invariants.


The System.Diagnostics.SymbolStore namespace provides classes that allow you to read and write debug symbol information, such as source line to Microsoft intermediate language (MSIL) maps. Compilers targeting the.NET Framework can store the debug symbol information into programmer's database (PDB) files. Debuggers and code profiler tools can read the debug symbol information at run time.


The System.Diagnostics.Tracing namespace provides types and members that enable you to create strongly typed events to be captured by event tracing for Windows (ETW).


The System.Diagnostics.Design namespace contains classes that can be used to extend design-time support for application monitoring and instrumentation.


The System.Diagnostics.CodeAnalysis namespace contains classes for interaction with code analysis tools. These tools are used to analyze code for conformance to coding conventions such as naming or security rules.

System.Diagnostics



The System.Diagnostics.Contracts.Internal namespace provides classes that the binary rewriter can use to handle a contract failure.


The System.Diagnostics.Contracts namespace contains static classes for representing program contracts such as preconditions, postconditions, and invariants.


The System.Diagnostics.SymbolStore namespace provides classes that allow you to read and write debug symbol information, such as source line to Microsoft intermediate language (MSIL) maps. Compilers targeting the.NET Framework can store the debug symbol information into programmer's database (PDB) files. Debuggers and code profiler tools can read the debug symbol information at run time.


The System.Diagnostics.Tracing namespace provides types and members that enable you to create strongly typed events to be captured by event tracing for Windows (ETW).


The System.Diagnostics.Design namespace contains classes that can be used to extend design-time support for application monitoring and instrumentation.


The System.Diagnostics.CodeAnalysis namespace contains classes for interaction with code analysis tools. These tools are used to analyze code for conformance to coding conventions such as naming or security rules.

System.Diagnostics

The System.Diagnostics namespace provides classes that allow you to interact with system processes, event logs, and performance counters.



The System.Diagnostics.Contracts.Internal namespace provides classes that the binary rewriter can use to handle a contract failure.


The System.Diagnostics.Contracts namespace contains static classes for representing program contracts such as preconditions, postconditions, and invariants.


The System.Diagnostics.SymbolStore namespace provides classes that allow you to read and write debug symbol information, such as source line to Microsoft intermediate language (MSIL) maps. Compilers targeting the.NET Framework can store the debug symbol information into programmer's database (PDB) files. Debuggers and code profiler tools can read the debug symbol information at run time.


The System.Diagnostics.Tracing namespace provides types and members that enable you to create strongly typed events to be captured by event tracing for Windows (ETW).


The System.Diagnostics.Design namespace contains classes that can be used to extend design-time support for application monitoring and instrumentation.


The System.Diagnostics.CodeAnalysis namespace contains classes for interaction with code analysis tools. These tools are used to analyze code for conformance to coding conventions such as naming or security rules.

System.Drawing

The System.Drawing namespace provides access to GDI+ basic graphics functionality. More advanced functionality is provided in the System.Drawing.Drawing2D, System.Drawing.Imaging, and System.Drawing.Text namespaces.


The System.Drawing.Design namespace contains classes that extend design-time user interface (UI) logic and drawing.


The System.Drawing.Drawing2D namespace provides advanced two-dimensional and vector graphics functionality.


The System.Drawing.Imaging namespace provides advanced GDI+ imaging functionality. Basic graphics functionality is provided by the System.Drawing namespace.


The System.Drawing.Printing namespace provides print-related services for Windows Forms applications.


The System.Drawing.Text namespace provides advanced GDI+ typography functionality.

System.Dynamic

The System.Dynamic namespace provides classes and interfaces that support Dynamic Language Runtime.

System.Globalization

The System.Globalization namespace contains classes that define culture-related information, including language, country/region, calendars in use, format patterns for dates, currency, and numbers, and sort order for strings. These classes are useful for writing globalized (internationalized) applications. Classes such as StringInfo and TextInfo provide advanced globalization functionalities, including surrogate support and text element processing.

System.IO

The System.IO namespace contains classes for reading and writing data from streams and interacting with the filesystem.

The System.IO.IsolatedStorage namespace contains types that allow the creation and use of isolated stores. With these stores, you can read and write data that less trusted code cannot access and prevent the exposure of sensitive information that can be saved elsewhere on the file system. Data is stored in compartments that are isolated by the current user and by the assembly in which the code exists. Additionally, data can be isolated by domain. Roaming profiles can be used in conjunction with isolated storage so isolated stores will travel with the user's profile. The IsolatedStorageScope enumeration indicates different types of isolation. For more information about when to use isolated storage, see Isolated Storage.


The System.IO.MemoryMappedFiles namespace provides classes for using a memory-mapped file, which maps the contents of a file to an application’s logical address space.


The System.IO.Pipes namespace contains types that provide a means for interprocess communication through anonymous and/or named pipes.


The System.IO.Compression namespace contains classes that provide basic compression and decompression services for streams.


The System.IO.Ports namespace contains classes for controlling serial ports. The most important class, SerialPort, provides a framework for synchronous and event-driven I/O, access to pin and break states, and access to serial driver properties. It can be used to wrap a Stream objects, allowing the serial port to be accessed by classes that use streams.

System.IO


The System.IO.IsolatedStorage namespace contains types that allow the creation and use of isolated stores. With these stores, you can read and write data that less trusted code cannot access and prevent the exposure of sensitive information that can be saved elsewhere on the file system. Data is stored in compartments that are isolated by the current user and by the assembly in which the code exists. Additionally, data can be isolated by domain. Roaming profiles can be used in conjunction with isolated storage so isolated stores will travel with the user's profile. The IsolatedStorageScope enumeration indicates different types of isolation. For more information about when to use isolated storage, see Isolated Storage.


The System.IO.MemoryMappedFiles namespace provides classes for using a memory-mapped file, which maps the contents of a file to an application’s logical address space.


The System.IO.Pipes namespace contains types that provide a means for interprocess communication through anonymous and/or named pipes.


The System.IO.Compression namespace contains classes that provide basic compression and decompression services for streams.


The System.IO.Ports namespace contains classes for controlling serial ports. The most important class, SerialPort, provides a framework for synchronous and event-driven I/O, access to pin and break states, and access to serial driver properties. It can be used to wrap a Stream objects, allowing the serial port to be accessed by classes that use streams.

System.IO


The System.IO.IsolatedStorage namespace contains types that allow the creation and use of isolated stores. With these stores, you can read and write data that less trusted code cannot access and prevent the exposure of sensitive information that can be saved elsewhere on the file system. Data is stored in compartments that are isolated by the current user and by the assembly in which the code exists. Additionally, data can be isolated by domain. Roaming profiles can be used in conjunction with isolated storage so isolated stores will travel with the user's profile. The IsolatedStorageScope enumeration indicates different types of isolation. For more information about when to use isolated storage, see Isolated Storage.


The System.IO.MemoryMappedFiles namespace provides classes for using a memory-mapped file, which maps the contents of a file to an application’s logical address space.


The System.IO.Pipes namespace contains types that provide a means for interprocess communication through anonymous and/or named pipes.


The System.IO.Compression namespace contains classes that provide basic compression and decompression services for streams.


The System.IO.Ports namespace contains classes for controlling serial ports. The most important class, SerialPort, provides a framework for synchronous and event-driven I/O, access to pin and break states, and access to serial driver properties. It can be used to wrap a Stream objects, allowing the serial port to be accessed by classes that use streams.

System.IO

The System.IO namespace contains types that allow reading and writing to files and data streams, and types that provide basic file and directory support.


The System.IO.IsolatedStorage namespace contains types that allow the creation and use of isolated stores. With these stores, you can read and write data that less trusted code cannot access and prevent the exposure of sensitive information that can be saved elsewhere on the file system. Data is stored in compartments that are isolated by the current user and by the assembly in which the code exists. Additionally, data can be isolated by domain. Roaming profiles can be used in conjunction with isolated storage so isolated stores will travel with the user's profile. The IsolatedStorageScope enumeration indicates different types of isolation. For more information about when to use isolated storage, see Isolated Storage.


The System.IO.MemoryMappedFiles namespace provides classes for using a memory-mapped file, which maps the contents of a file to an application’s logical address space.


The System.IO.Pipes namespace contains types that provide a means for interprocess communication through anonymous and/or named pipes.


The System.IO.Compression namespace contains classes that provide basic compression and decompression services for streams.


The System.IO.Ports namespace contains classes for controlling serial ports. The most important class, SerialPort, provides a framework for synchronous and event-driven I/O, access to pin and break states, and access to serial driver properties. It can be used to wrap a Stream objects, allowing the serial port to be accessed by classes that use streams.

System.Json

System.Linq

The System.Linq namespace provides classes and interfaces that support queries that use vbteclinqext.


The System.Linq.Expressions namespace contains classes, interfaces and enumerations that enable language-level code expressions to be represented as objects in the form of expression trees.

System.Media

The System.Media namespace contains classes for playing sound files and accessing sounds provided by the system.

System.Messaging.Design

The System.Messaging.Design namespace contains classes that can be used to extend design-time support for System.Messaging classes.

System.Net

The System.Net namespace provides a simple programming interface for many of the protocols used on networks today. The WebRequest and WebResponse classes form the basis of what are called pluggable protocols, an implementation of network services that enables you to develop applications that use Internet resources without worrying about the specific details of the individual protocols.

Classes in the System.Net namespace can be used to develop Windows Store apps or desktop apps. When used in a Windows Store app, classes in the System.Net namespace are affected by network isolation feature, part of the application security model used by the Windows Developer Preview. The appropriate network capabilities must be enabled in the app manifest for a Windows Store app for the system to allow network access by a Windows Store app. For more information, see the Network Isolation for Windows Store Apps.


Provides support for collections of HTTP headers used by the System.Net.Http namespace


The System.Net.Http namespace provides a programming interface for modern HTTP applications.


The System.Net.Cache namespace defines the types and enumerations used to define cache policies for resources obtained using the WebRequest and HttpWebRequest classes.


The System.Net.Configuration namespace contains classes that applications use to programmatically access and update configuration settings for the System.Net namespaces.


The System.Net.Mail namespace contains classes used to send electronic mail to a Simple Mail Transfer Protocol (SMTP) server for delivery.


The System.Net.Mime namespace holds types that are used to represent Multipurpose Internet Mail Exchange (MIME) headers. These types are used with the types in the System.Net.Mail namespace to specify Content-Type, Content-Disposition and Content-transfer-Encoding headers when using the SmtpClient class to send e-mail.


The System.Net.NetworkInformation namespace provides access to network traffic data, network address information, and notification of address changes for the local computer. The namespace also contains classes that implement the Ping utility. You can use Ping and related classes to check whether a computer is reachable across the network.


The System.Net.Security namespace provides network streams for secure communications between hosts.


The System.Net.Sockets namespace provides a managed implementation of the Windows Sockets (Winsock) interface for developers who need to tightly control access to the network.


The System.Net.WebSockets namespace provides a managed implementation of the WebSocket interface for developers.

System.Reflection

The System.Reflection namespace contains types that retrieve information about assemblies, modules, members, parameters, and other entities in managed code by examining their metadata. These types also can be used to manipulate instances of loaded types, for example to hook up events or to invoke methods. To dynamically create types, use the System.Reflection.Emit namespace.


 

The System.Reflection.Emit namespace contains classes that allow a compiler or tool to emit metadata and Microsoft intermediate language (MSIL) and optionally generate a PE file on disk. The primary clients of these classes are script engines and compilers.

System.Resources

 

The System.Resources.Tools namespace contains the StronglyTypedResourceBuilder class, which provides support for strongly-typed resources. Beginning with the .NET Framework version 2.0, this compile-time feature encapsulates access to resources by creating classes that contain a set of static read-only (get) properties, thus making it easier to consume resources.

System.Resources

The System.Resources namespace provides classes and interfaces that allow developers to create, store, and manage various culture-specific resources used in an application. One of the most important classes of the System.Resources namespace is the ResourceManager class.


The System.Resources.Tools namespace contains the StronglyTypedResourceBuilder class, which provides support for strongly-typed resources. Beginning with the .NET Framework version 2.0, this compile-time feature encapsulates access to resources by creating classes that contain a set of static read-only (get) properties, thus making it easier to consume resources.

System.Runtime

The System.Runtime namespace contains advanced types that support diverse namespaces such as the System, Runtime, and the Security namespaces.


 

The System.Runtime.ConstrainedExecution namespace defines a set of types that enumerate and define a contract for reliability between the author of some code, and the developers who take a dependency on that code. The types in the System.Runtime.ConstrainedExecution namespace are intended for use in constrained execution regions (CERs).


The System.Runtime.ExceptionServices namespace provides classes for advanced exception handling.


The System.Runtime.Hosting namespace contains advanced types that are used in application activation within application domains.



The System.Runtime.InteropServices.Expando namespace contains the IExpando interface which allows modification of an object by adding or removing its members.


 

The System.Runtime.InteropServices.WindowsRuntime namespace contains classes that support interoperation between managed code and the wrt, and that enable the creation of wrt types with managed code.


 

The System.Runtime.Remoting.Activation namespace provides classes and objects that support server and client activation of remote objects.


 

The System.Runtime.Remoting.Contexts namespace contains objects that define the contexts all objects reside within. A context is an ordered sequence of properties that defines an environment for the objects within it. Contexts are created during the activation process for objects that are configured to require certain automatic services such synchronization, transactions, just-in-time (JIT) activation, security, and so on. Multiple objects can live inside a context.


The System.Runtime.Remoting.Lifetime namespace contains classes that manage the lifetime of remote objects.


The System.Runtime.Remoting.Messaging namespace contains classes used to create and transmit messages. The remoting infrastructure uses messages to communicate with remote objects. Messages are used to transmit remote method calls, to activate remote objects, and to communicate information. A message object carries a set of named properties, including action identifiers, envoy information, and parameters. Some of the most important classes of the System.Runtime.Remoting.Messaging namespace are the AsyncResult class, the RemotingSurrogateSelector class, and the ReturnMessage class.


The System.Runtime.Remoting.Metadata.W3cXsd2001 namespace contains the XML Schema Definition (XSD) that was defined by the World Wide Web Consortium (W3C) in 2001. The XML Schema Part 2: Datatypes specification from W3C identifies format and behavior of various data types. This namespace contains wrapper classes for the data types that conform to the W3C specification. All date and time types conform to the ISO standards specification.


The System.Runtime.Remoting.Metadata namespace contains classes and attributes that can be used to customize generation and processing of SOAP for objects and fields. The classes of this namespace can be used to indicate the SOAPAction header field, type output, XML element name, and the method XML namespace URI. This information is used by the SOAP serializer during SOAP generation and the Soapsuds Tool (Soapsuds.exe) during Web Services Description Language (WSDL) generation. The information specified by the attributes in this namespace can be used on the receiving end of the generated SOAP to customize processing of the remoted method calls and objects. One of the most important classes of the System.Runtime.Remoting.Metadata namespace is SoapAttribute class. The SoapAttribute class is nonfunctional, and can only be used as the base class for all the metadata attributes. For more information on the SOAPAction HTTP header field, see www.w3.org/tr/soap/#_Toc478383528.


The System.Runtime.Remoting.Proxies namespace contains classes that control and provide functionality for proxies. A proxy is a local object that is an image of a remote object. Proxies enable clients to access objects across remoting boundaries.


 

The System.Runtime.Remoting namespace provides classes and interfaces that allow developers to create and configure distributed applications. Some of the more important classes of the System.Runtime.Remoting namespace are the RemotingConfiguration class, the RemotingServices class, and the ObjRef class.


The System.Runtime.Serialization.Formatters.Binary namespace contains the BinaryFormatter class, which can be used to serialize and deserialize objects in binary format.


The System.Runtime.Serialization.Formatters namespace provides common enumerations, interfaces, and classes that are used by serialization formatters.


 


The System.Runtime.CompilerServices namespace provides functionality for compiler writers who use managed code to specify attributes in metadata that affect the run-time behavior of the common language runtime.


The System.Runtime.Remoting.Channels.Http namespace contains channels that use the HTTP protocol to transport messages and objects to and from remote locations. By default, the HTTP channels encode objects and method calls in SOAP format for transmission, but other encoding and decoding formatter sinks can be specified in the configuration properties of a channel. One of the most important classes of the System.Runtime.Remoting.Channels.Http namespace is the HttpChannel class.


The System.Runtime.Remoting.Channels.Ipc namespace defines a communication channel for remoting that uses the interprocess cmmunication (IPC) system of the Windows operating system. Because it does not use network communication, the IPC channel is much faster than the HTTP and TCP channels, but it can only be used for communication between application domains on the same physical computer.


The System.Runtime.Remoting.Channels.Tcp namespace contains channels that use the TCP protocol to transport messages and objects to and from remote locations. By default, the TCP channels encode objects and method calls in binary format for transmission, but other encoding and decoding formatter sinks can be specified in the configuration properties of a channel. One of the most important classes of the System.Runtime.Remoting.Channels.Tcp namespace is the TcpChannel class.


The System.Runtime.Remoting.Channels namespace contains classes that support and handle channels and channel sinks, which are used as the transport medium when a client calls a method on a remote object.


The System.Runtime.Remoting.MetadataServices namespace contains the classes that are used by the Soapsuds.exe command-line tool and the user code to convert metadata to and from XML schema for the remoting infrastructure. Some of the most important classes of this namespace are the SdlChannelSink class and the MetaData class.


The System.Runtime.Remoting.Services namespace contains service classes that provide functionality to the .NET Framework. One of the most important classes of this namespace is the TrackingServices class.


The System.Runtime.Serialization.Configuration namespace contains classes used to read the values found in application configuration under system.xml.serialization section.

The classes in this namespace are used by the serialization infrastructure to handle the configuration elements and cannot be used directly. Instead, to configure the DataContractSerializer, create an application configuration file and use the following XML elements. <system.xml.serialization><dataContractSerializer><declaredTypes><add> element for <declaredTypes><knownType> element


Provides classes related to Json serialization.


The System.Runtime.Serialization namespace contains classes that can be used for serializing and deserializing objects. Serialization is the process of converting an object or a graph of objects into a linear sequence of bytes for either storage or transmission to another location. Deserialization is the process of taking in stored information and recreating objects from it.


The System.Runtime.Serialization.Formatters.Soap namespace contains the SoapFormatter class, which can be used to serialize and deserialize objects in the SOAP format. When building applications that uses the types in this namespace, you must reference the System.Runtime.Serialization.Formatters.Soap.dll assembly.


The System.Runtime.InteropServices.ComTypes namespace contains methods that are defintions of COM functions for managed code. These functions replace the now-obsolete UCOM* methods in the System.Runtime.InteropServices namespace.


The System.Runtime.InteropServices namespace provides a wide variety of members that support COM interop and platform invoke services. If you are unfamiliar with these services, see Interoperating with Unmanaged Code.


The System.Runtime.Versioning namespace contains advanced types that support versioning in side by side implementations of the .NET Framework.

System.Security

The System.Security namespace provides the underlying structure of the common language runtime security system, including base classes for permissions.



 

 

 

The System.Security.Policy namespace contains code groups, membership conditions, and evidence. These three types of classes are used to create the rules applied by the common language runtime security policy system. Evidence classes are the input to security policy and membership conditions are the switches; together these create policy statements and determine the granted permission set. Policy levels and code groups are the structure of the policy hierarchy. Code groups are the encapsulation of a rule and are arranged hierarchically in a policy level.


The System.Security.Principal namespace defines a principal object that represents the security context under which code is running. For more information, see Role-Based Security.


 


The System.Security.Cryptography.Pkcs namespace provides programming elements for Public Key Cryptography Standards (PKCS), including methods for signing data, exchanging keys, requesting certificates, public key encryption and decryption, and other security functions.



The System.Security.Cryptography.Xml namespace contains classes to support the creation and validation of XML digital signatures. The classes in this namespace implement the World Wide Web Consortium Recommendation, "XML-Signature Syntax and Processing", described at http://www.w3.org/TR/xmldsig-core/.




The System.Security.AccessControl namespace provides programming elements that control access to and audit security-related actions on securable objects.


The System.Security.Authentication.ExtendedProtection.Configuration namespace provides support for configuration of authentication using extended protection for applications.


The System.Security.Authentication.ExtendedProtection namespace provides support for authentication using extended protection for applications.


The Authentication namespace provides a set of enumerations that describe the security of a connection. These enumerations include CipherAlgorithmType, ExchangeAlgorithmType, HashAlgorithmType, and SslProtocolType.


The System.Security.Cryptography.X509Certificates namespace contains the common language runtime implementation of the Authenticode X.509 v.3 certificate. This certificate is signed with a private key that uniquely and positively identifies the holder of the certificate.


The System.Security.Cryptography namespace provides cryptographic services, including secure encoding and decoding of data, as well as many other operations, such as hashing, random number generation, and message authentication. For more information, see Cryptographic Services.


The System.Security.Permissions namespace defines classes that control access to operations and resources based on policy.

System.ServiceModel

Provides classes related to the service model.


Represents the configuration settings for the SMSvcHost.exe tool.

This namespace represents the configuration elements that can be configured in the SMSvcHost.exe.config file. Specifically, it includes all machine-wide settings that need to be configured.


Provides classes related to service model activation.


Provides classes related to service model channels.


Defines classes needed for integration with COM applications.


Provides classes related to service model configuration.


Provides classes related to the service model description.


The System.ServiceModel.Diagnostics namespace contains an enumeration that is used to configure performance counters for diagnostics purposes.


Provides classes related to dispatching the service model.


The System.ServiceModel.MsmqIntegration namespace contains classes that relate to Microsoft Message Queuing Service (MSMQ) integration, which allows communication between MSMQ applications and indigo1 applications.


The System.ServiceModel.PeerResolvers namespace contains classes that allow developers to customize and extend the Peer Name Resolution Protocol service.


Deals with security tokens and certificates.


The System.ServiceModel.Security namespace deals with general security-related topics, for example, SecurityAlgorithmSuite.


Provides classes related to service model syndication.

System.ServiceProcess.Design

The System.ServiceProcess.Design namespace contains classes that can be used to extend design-time support for Windows services applications.

System.Text

The System.Text namespace contains classes that represent ASCII and Unicode character encodings; abstract base classes for converting blocks of characters to and from blocks of bytes; and a helper class that manipulates and formats String objects without creating intermediate instances of String.


The System.Text.RegularExpressions namespace contains classes that provide access to the .NET Framework regular expression engine. The namespace provides regular expression functionality that may be used from any platform or language that runs within the Microsoft .NET Framework. In addition to the types contained in this namespace, the RegexStringValidator class enables you to determine whether a particular string conforms to a regular expression pattern.

System.Threading

This namespace provides the core classes for multi-threaded programming, including the Thread class to launch threads as well as several classes for synchronization and multi-threaded resource management.


The System.Threading.Tasks namespace provides types that simplify the work of writing concurrent and asynchronous code. The main types are Task which represents an asynchronous operation that can be waited on and cancelled, and Task`1, which is a task that can return a value. The TaskFactory class provides static methods for creating and starting tasks, and the TaskScheduler class provides the default thread scheduling infrastructure.

System.Threading



The System.Threading.Tasks namespace provides types that simplify the work of writing concurrent and asynchronous code. The main types are Task which represents an asynchronous operation that can be waited on and cancelled, and Task`1, which is a task that can return a value. The TaskFactory class provides static methods for creating and starting tasks, and the TaskScheduler class provides the default thread scheduling infrastructure.

System.Threading

The System.Threading namespace provides classes and interfaces that enable multithreaded programming. In addition to classes for synchronizing thread activities and access to data (Mutex, Monitor, Interlocked, AutoResetEvent, and so on), this namespace includes a ThreadPool class that allows you to use a pool of system-supplied threads, and a Timer class that executes callback methods on thread pool threads.



The System.Threading.Tasks namespace provides types that simplify the work of writing concurrent and asynchronous code. The main types are Task which represents an asynchronous operation that can be waited on and cancelled, and Task`1, which is a task that can return a value. The TaskFactory class provides static methods for creating and starting tasks, and the TaskScheduler class provides the default thread scheduling infrastructure.

System.Timers

The System.Timers namespace provides the Timer component, which allows you to raise an event on a specified interval.

System.Web


The System.Web.UI.Design.WebControls namespace contains classes that can be used to extend design-time support for Web server controls.


The System.Web.UI.Design namespace contains classes that can be used to extend design-time support for ASP.NET Web pages and for Web server controls.


The System.Web.Services.Configuration namespace consists of the classes that configure how XML Web services created using ASP.NET run.


The System.Web.Services.Description namespace consists of the classes that enable you to publicly describe an XML Web service by using the Web Services Description Language (WSDL). 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. For more information about WSDL, see the specification at the W3C Web site (http://www.w3.org/TR/wsdl/).


The System.Web.Services.Discovery namespace consists of the classes that allows XML Web service clients to locate the available XML Web services on a Web server through a process called XML Web services Discovery.


The System.Web.Services.Protocols namespace consists of the classes that define the protocols used to transmit data across the wire during the communication between XML Web service clients and XML Web services created using ASP.NET.


The System.Web.Services namespace consists of the classes that enable you to create XML Web services using ASP.NET and XML Web service clients. XML Web services are applications that provide the ability to exchange messages in a loosely coupled environment using standard protocols such as HTTP, XML, XSD, SOAP, and WSDL. XML Web services enable the building of modular applications within and across companies in heterogeneous environments making them interoperable with a broad variety of implementations, platforms and devices. The SOAP-based XML messages of these applications can have well-defined (structured and typed), or loosely defined parts (using arbitrary XML). The ability of the messages to evolve over time without breaking the protocol is fundamental to the flexibility and robustness of XML Web services as a building block for the future of the Web.


The System.Web.Caching namespace provides classes for caching frequently used data on the server.


The System.Web.Compilation namespace contains classes for generating and compiling custom file types within the ASP.NET build environment.


The System.Web.Configuration.Internal namespace contains configuration types intended for internal use only.


The System.Web.Configuration namespace contains classes that are used to set up ASP.NET configuration.


The System.Web.Handlers namespace contains HTTP handler classes that process HTTP requests to a Web server.


The System.Web.Hosting namespace provides the functionality for hosting ASP.NET applications from managed applications outside Microsoft Internet Information Services (IIS).


The classes in this namespace have been deprecated. Use the System.Net.Mail namespace instead. The System.Web.Mail namespace contains classes that enable you to construct and send messages using the CDOSYS (Collaboration Data Objects for Windows 2000) message component. The mail message is delivered either through the SMTP mail service built into Microsoft Windows 2000 or through an arbitrary SMTP server. The classes in this namespace can be used from ASP.NET or from any managed application.


The System.Web.Management namespace contains classes and interfaces for managing and monitoring the health of Web applications.


The System.Web.Profile namespace contains classes that are used to work with ASP.NET user profiles in Web server applications.


The System.Web.Security namespace contains classes that are used to implement ASP.NET security in Web server applications.


The System.Web.SessionState namespace supplies classes and interfaces that enable storage of data specific to a single client within a Web application on the server. The session-state data is used to give the client the appearance of a persistent connection with the application. State information can be stored within local process memory or, for Web farm configurations, it can be stored out of process using either the ASP.NET State service or a Microsoft SQL Server database.


The System.Web.UI.Adapters namespace contains the base classes for control adapters and page adapters. You can use these adapters to override the life-cycle states of pages and controls. This is useful if you want to modify a control's markup or behavior for new markup standards or for specific browsers.


The System.Web.UI.HtmlControls namespace contains classes that allow you to create HTML server controls on a Web Forms page. HTML server controls run on the server and map directly to standard HTML tags supported by most browsers. This allows you to programmatically control the HTML elements on a Web Forms page.


The System.Web.UI.WebControls.Adapters namespace contains classes that you can use to override the life-cycle stages of a Web control. The classes enable you to modify a control's markup or behavior for new markup standards or for specific browsers.


The System.Web.UI.WebControls.WebParts namespace contains classes and interfaces known collectively as the Web Parts control set. You can use these classes to create Web pages whose appearance and behavior can be modified (personalized) by end users. Each user's personalized settings for a page are saved for future browser sessions.


The System.Web.UI.WebControls namespace contains classes that allow you to 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-purpose controls such as a calendar. Because Web server controls run on the server, you can programmatically control these elements. Although Web server controls are rendered as HTML, their object model does not necessarily reflect HTML syntax.


The System.Web.Util namespace is a collection of classes that enable callback methods to be run under the scope of a transaction and that enable work to be posted to separate threads.

System.Web

The System.Web namespace supplies classes and interfaces that enable browser-server communication. This namespace includes the HttpRequest class, which provides extensive information about the current HTTP request; the HttpResponse class, which manages HTTP output to the client; and the HttpServerUtility class, which provides access to server-side utilities and processes. System.Web also includes classes for cookie manipulation, file transfer, exception information, and output cache control.


The System.Web.UI.Design.WebControls namespace contains classes that can be used to extend design-time support for Web server controls.


The System.Web.UI.Design namespace contains classes that can be used to extend design-time support for ASP.NET Web pages and for Web server controls.


The System.Web.Services.Configuration namespace consists of the classes that configure how XML Web services created using ASP.NET run.


The System.Web.Services.Description namespace consists of the classes that enable you to publicly describe an XML Web service by using the Web Services Description Language (WSDL). 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. For more information about WSDL, see the specification at the W3C Web site (http://www.w3.org/TR/wsdl/).


The System.Web.Services.Discovery namespace consists of the classes that allows XML Web service clients to locate the available XML Web services on a Web server through a process called XML Web services Discovery.


The System.Web.Services.Protocols namespace consists of the classes that define the protocols used to transmit data across the wire during the communication between XML Web service clients and XML Web services created using ASP.NET.


The System.Web.Services namespace consists of the classes that enable you to create XML Web services using ASP.NET and XML Web service clients. XML Web services are applications that provide the ability to exchange messages in a loosely coupled environment using standard protocols such as HTTP, XML, XSD, SOAP, and WSDL. XML Web services enable the building of modular applications within and across companies in heterogeneous environments making them interoperable with a broad variety of implementations, platforms and devices. The SOAP-based XML messages of these applications can have well-defined (structured and typed), or loosely defined parts (using arbitrary XML). The ability of the messages to evolve over time without breaking the protocol is fundamental to the flexibility and robustness of XML Web services as a building block for the future of the Web.


The System.Web.Caching namespace provides classes for caching frequently used data on the server.


The System.Web.Compilation namespace contains classes for generating and compiling custom file types within the ASP.NET build environment.


The System.Web.Configuration.Internal namespace contains configuration types intended for internal use only.


The System.Web.Configuration namespace contains classes that are used to set up ASP.NET configuration.


The System.Web.Handlers namespace contains HTTP handler classes that process HTTP requests to a Web server.


The System.Web.Hosting namespace provides the functionality for hosting ASP.NET applications from managed applications outside Microsoft Internet Information Services (IIS).


The classes in this namespace have been deprecated. Use the System.Net.Mail namespace instead. The System.Web.Mail namespace contains classes that enable you to construct and send messages using the CDOSYS (Collaboration Data Objects for Windows 2000) message component. The mail message is delivered either through the SMTP mail service built into Microsoft Windows 2000 or through an arbitrary SMTP server. The classes in this namespace can be used from ASP.NET or from any managed application.


The System.Web.Management namespace contains classes and interfaces for managing and monitoring the health of Web applications.


The System.Web.Profile namespace contains classes that are used to work with ASP.NET user profiles in Web server applications.


The System.Web.Security namespace contains classes that are used to implement ASP.NET security in Web server applications.


The System.Web.SessionState namespace supplies classes and interfaces that enable storage of data specific to a single client within a Web application on the server. The session-state data is used to give the client the appearance of a persistent connection with the application. State information can be stored within local process memory or, for Web farm configurations, it can be stored out of process using either the ASP.NET State service or a Microsoft SQL Server database.


The System.Web.UI.Adapters namespace contains the base classes for control adapters and page adapters. You can use these adapters to override the life-cycle states of pages and controls. This is useful if you want to modify a control's markup or behavior for new markup standards or for specific browsers.


The System.Web.UI.HtmlControls namespace contains classes that allow you to create HTML server controls on a Web Forms page. HTML server controls run on the server and map directly to standard HTML tags supported by most browsers. This allows you to programmatically control the HTML elements on a Web Forms page.


The System.Web.UI.WebControls.Adapters namespace contains classes that you can use to override the life-cycle stages of a Web control. The classes enable you to modify a control's markup or behavior for new markup standards or for specific browsers.


The System.Web.UI.WebControls.WebParts namespace contains classes and interfaces known collectively as the Web Parts control set. You can use these classes to create Web pages whose appearance and behavior can be modified (personalized) by end users. Each user's personalized settings for a page are saved for future browser sessions.


The System.Web.UI.WebControls namespace contains classes that allow you to 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-purpose controls such as a calendar. Because Web server controls run on the server, you can programmatically control these elements. Although Web server controls are rendered as HTML, their object model does not necessarily reflect HTML syntax.


The System.Web.Util namespace is a collection of classes that enable callback methods to be run under the scope of a transaction and that enable work to be posted to separate threads.

System.Windows.Forms

The System.Windows.Forms namespace contains classes for creating Windows-based applications that take full advantage of the rich user interface features available in the Microsoft Windows operating system.


The System.Windows.Forms.ComponentModel.Com2Interop namespace contains helper classes that Visual Studio uses to display property pages while in design mode.


The System.Windows.Forms.Design namespace contains classes that support design-time configuration and behavior for Windows Forms components. These classes consist of designer classes that provide support for Windows Forms components, a set of design-time services; UITypeEditor classes for configuring certain types of properties, and classes for importing ActiveX controls.


The System.Windows.Forms.Layout namespace contains classes for implementing layout behaviors in your form or control.


The PropertyGridInternal namespace provides internal support for the PropertyGrid control. The classes in this namespace support the .NET Framework infrastructure and are not intended to be used directly from your code.


The System.Windows.Forms.VisualStyles namespace contains classes for rendering controls and other Windows user interface (UI) elements with visual styles in operating systems that support them.



The System.Windows.Forms.Design.Behavior namespace contains classes for creating custom user interface behavior for components at design time.


System.Windows.Input

Provides types to support the TLA#tla_wpf input system. This includes device abstraction classes for mouse, keyboard, and stylus devices, a common input manager class, support for commanding and custom commands, and various utility classes.

System.Xml

The System.Xml namespace provides standards-based support for processing XML.


The System.Xml.Schema namespace contains the XML classes that provide standards-based support for XML schema definition language (XSD) schemas.


The System.Xml.Serialization.Advanced namespace contains classes that allow you to customize the code generated from a Web Services Description Language (WSDL) document.


The System.Xml.Serialization.Configuration namespace contains classes used to read the values found in application configuration files under the system.xml.serialization section.


The System.Xml.Serialization namespace contains classes that are used to serialize objects into XML format documents or streams.


The System.Xml.XPath namespace contains the classes that define a cursor model for navigating and editing XML information items as instances of the XQuery 1.0 and XPath 2.0 Data Model.


The System.Xml.Xsl namespace provides support for Extensible Stylesheet Transformation (XSLT) transforms. It supports the W3C XSL Transformations (XSLT) Version 1.0 Recommendation (www.w3.org/TR/xslt).


Contains the classes for LINQ to XML. LINQ to XML is an in-memory XML programming interface that enables you to modify XML documents efficiently and easily.



System.Xml


The System.Xml.Schema namespace contains the XML classes that provide standards-based support for XML schema definition language (XSD) schemas.


The System.Xml.Serialization.Advanced namespace contains classes that allow you to customize the code generated from a Web Services Description Language (WSDL) document.


The System.Xml.Serialization.Configuration namespace contains classes used to read the values found in application configuration files under the system.xml.serialization section.


The System.Xml.Serialization namespace contains classes that are used to serialize objects into XML format documents or streams.


The System.Xml.XPath namespace contains the classes that define a cursor model for navigating and editing XML information items as instances of the XQuery 1.0 and XPath 2.0 Data Model.


The System.Xml.Xsl namespace provides support for Extensible Stylesheet Transformation (XSLT) transforms. It supports the W3C XSL Transformations (XSLT) Version 1.0 Recommendation (www.w3.org/TR/xslt).


Contains the classes for LINQ to XML. LINQ to XML is an in-memory XML programming interface that enables you to modify XML documents efficiently and easily.



System.Xml

The System.Xml namespace contains classes for reading, writing, and manipulating Xml documents.

The System.Xml.Schema namespace contains the XML classes that provide standards-based support for XML schema definition language (XSD) schemas.


The System.Xml.Serialization.Advanced namespace contains classes that allow you to customize the code generated from a Web Services Description Language (WSDL) document.


The System.Xml.Serialization.Configuration namespace contains classes used to read the values found in application configuration files under the system.xml.serialization section.


The System.Xml.Serialization namespace contains classes that are used to serialize objects into XML format documents or streams.


The System.Xml.XPath namespace contains the classes that define a cursor model for navigating and editing XML information items as instances of the XQuery 1.0 and XPath 2.0 Data Model.


The System.Xml.Xsl namespace provides support for Extensible Stylesheet Transformation (XSLT) transforms. It supports the W3C XSL Transformations (XSLT) Version 1.0 Recommendation (www.w3.org/TR/xslt).


Contains the classes for LINQ to XML. LINQ to XML is an in-memory XML programming interface that enables you to modify XML documents efficiently and easily.