This documentation is archived and is not being maintained.


.NET Framework 1.1

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z 

A logical naming scheme for grouping related types. The .NET Framework uses a hierarchical naming scheme for grouping types into logical categories of related functionality, such as the ASP.NET technology or remoting functionality. Design tools can use namespaces to make it easier for developers to browse and reference types in their code. A single assembly can contain types whose hierarchical names have different namespace roots, and a logical namespace root can span multiple assemblies. In the .NET Framework, a namespace is a logical design-time naming convenience, whereas an assembly establishes the name scope for types at run time. See also: assembly.
naming container
Any ASP.NET control that implements the INamingContainer interface. This is a marker interface that enables a control to create a new naming scope under itself so that ID attributes assigned to its child controls are unique within the entire ASP.NET page that contains the control.
native code
Code that has been compiled to processor-specific machine code.
nested type
A type defined within the scope of another type. A nested type is typically used for encapsulating the implementation details of the top-level type.
.NET Compact Framework
A hardware-independent environment for running programs on resource-constrained computing devices. It inherits the full .NET Framework architecture of the common language runtime, supports a subset of the .NET Framework class library, and contains classes designed exclusively for the .NET Compact Framework. Supported devices include personal data assistants (PDAs) (such as the Pocket PC), mobile phones, set-top boxes, automotive computing devices, and custom-designed embedded devices built with the Microsoft Windows CE.NET operating system.
.NET Framework data provider
A component of ADO.NET that provides access to data from a relational data source. A .NET Framework data provider contains classes to connect to a data source, execute commands at the data source, and return query results from the data source, including the ability to execute commands within transactions. A .NET Framework data provider also contains classes to populate a DataSet with results from a data source and propagate changes in a DataSet back to the data source.
.NET Framework
An integral Windows component that supports building and running the next generation of applications and XML Web services. It provides a highly productive, standards-based, multilanguage environment for integrating existing investments with next generation applications and services, as well as the agility to solve the challenges of deployment and operation of Internet-scale applications. The .NET Framework consists of three main parts: the common language runtime, a hierarchical set of unified class libraries, and a componentized version of ASP called ASP.NET. See also: ASP.NET, common language runtime, .NET Framework class library.
.NET Framework class library
A CLS-compliant library of classes, interfaces, and value types that are included in the Microsoft .NET Framework SDK. This library provides access to system functionality and is designed to be the foundation on which .NET Framework applications, components, and controls are built. See also: class, CLS-compliant, Common Language Specification, interface, value type.