C

  • Article

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 

  • C#
    A new programming language designed for building enterprise applications that run on the .NET Framework. C#, which is an evolution of C and C++, is type safe and object oriented. Because it is compiled as managed code, it benefits from the services of the common language runtime, such as language interoperability, security, and garbage collection.

  • card
    A Web page in WML.

    WML devices can either display the contents of a card on a single screen or, when necessary, provide scroll bars so that the entire contents of the card can be viewed.

    Developers need not worry about manipulating cards or decks (groups of cards) because ASP.NET mobile controls handle formatting, including pagination, for targeted devices. See also: deck, WML.

  • CCW
    See definition for COM callable wrapper.

  • cHTML
    A markup language used on some cell phones. cHTML is a subset of HTML with additional tags to enhance mobile functionality.

  • class
    A reference type that encapsulates data (constants and fields) and behavior (methods, properties, indexers, events, operators, instance constructors, static constructors, and destructors), and can contain nested types. Class types support inheritance, a mechanism whereby a derived class can extend and specialize a base class. See also: encapsulation, indexer, property, reference type.

  • CLR
    See definition for common language runtime.

  • CLS
    See definition for Common Language Specification (CLS).

  • CLS-compliant
    Code that publicly exposes only language features that are in the Common Language Specification. CLS compliance can apply to classes, interfaces, components, and tools. See also: Common Language Specification (CLS).

  • code access security
    A mechanism provided by the common language runtime whereby managed code is granted permissions by security policy and these permissions are enforced, helping to limit the operations that the code will be allowed to perform. To help prevent unintended code paths from exposing a security vulnerability, all callers on the call stack must be granted the necessary permissions (possibly subject to override by assertion or denial). See also: assertion, denial.

  • code-behind class
    A class that is accessed by an .aspx file, but resides in a separate file (such as a .dll or .cs file). For example, you can write a code-behind class that creates an ASP.NET custom server control, contains code that is called from an .aspx file, but does not reside within the .aspx file.

  • code-behind file
    A code file containing the page class that implements the program logic of a Web Forms or ASP.NET mobile Web Forms application.

  • code-behind page
    See definition for code-behind file.

  • COM callable wrapper (CCW)
    A proxy object generated by the common language runtime so that existing COM applications can use managed classes, including .NET Framework classes, transparently.

  • COM interop
    A service that enables .NET Framework objects to communicate with COM objects.

  • common language runtime
    The engine at the core of managed code execution. The runtime supplies managed code with services such as cross-language integration, code access security, object lifetime management, and debugging and profiling support.

  • common language runtime host
    An unmanaged application that uses a set of APIs, called the hosting interfaces, to integrate managed code into the application. Common language runtime hosts often require a high degree of customization over the runtime that is loaded into the process. The hosting interfaces allow common language runtime hosts to specify settings that configure the garbage collector, select the appropriate build for their environment (server versus workstation), and so on. Common language runtime hosts often support an extensibility model that allows the end user to dynamically add new pieces of functionality, such as a new control or a user-written function. These extensions are typically isolated from each other in the process using application domains and custom security settings. Examples of common language runtime hosts include ASP.NET, Microsoft Internet Explorer, and a host to run executables launched from the Windows Shell. See also: application domain, common language runtime, managed code.

  • Common Language Specification (CLS)
    A subset of language features supported by the common language runtime, including features common to several object-oriented programming languages. CLS-compliant components and tools are guaranteed to interoperate with other CLS-compliant components and tools. See also: CLS-compliant.

  • common object file format (COFF)
    A format in 32-bit programming for executable (image) and object files that is portable across platforms. The Microsoft implementation is called portable executable (PE) file format. See also: portable executable (PE) file.

  • common type system
    The specification that determines how the common language runtime defines, uses, and manages types.

  • comparison evaluator
    A filter that compares a device capability name to a value. See also: device capabilities.

  • composite control
    A custom server control that consists of a custom collection of other server controls as child controls.

  • container
    See definition for naming container.

  • container control
    A type of ASP.NET mobile control that contains other controls and provides visual groupings of controls and content.

  • context
    An ordered sequence of properties that define an environment for the objects resident inside it. Contexts are created during the activation process for objects that are configured to require certain automatic services such as synchronization, transactions, just-in-time activation, security, and so on. Multiple objects can live inside a context.

  • context property
    The implicit state, and code to manage that state, held on behalf of an object instance. For example, the transaction context property holds the transaction identifier of the transaction that the object is participating in.

  • contract
    The behavior and state that a class provides, which is matched with what a client of that class can expect to hold. A contract is expressed partly by the signatures for all public fields, methods, properties, and events of that class. This is augmented by a description (usually in simple descriptive text) of what each field or property represents, together with what each method does.

  • custom attribute (Attribute)
    A class used to represent custom metadata.

  • custom control
    A control authored by a user or a third-party software vendor that does not belong to the .NET Framework class library. This is a generic term that also includes user controls. Custom server controls are used in Web Forms (ASP.NET pages). Custom client controls are used in Windows Forms applications.