لغت نامه

Visual Studio and .NET Framework

Part1:(A-C)III

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.

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 other term: 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 Information Model (CIM)

In WMI, the model that describes how to represent real-world managed objects. CIM uses an object-oriented paradigm, where managed objects are modeled using the concepts of classes and instances. The CIM is divided into the metamodel and the standard schema. The metamodel describes what types of entities make up the schema. It also defines how these entities can be combined into objects that represent real-world devices.

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.

communication pipeline

See other term: pipeline

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.

conceptual model

An abstract specification for the entity types, associations, entity containers, entity sets, and association sets in the domain of an application built on the ADO.NET Entity Framework.

conceptual schema definition language (CSDL)

An XML-based language that is used to define the entity types, associations, entity containers, entity sets, and association sets of a conceptual model.

configuration file

An XML file with the .config extension that contains option settings for an application or Web site. Common configuration files include Machine.config and Web.config.

connection

See other term: Web Parts connection

connection point

A System.Web.UI.WebControls.WebParts.ConnectionPoint object associated with the provider and consumer controls that participate in Web Parts connections. A connection point manages the exchange of data between the controls. Providers and consumers each have their own connection points. See also: consumer, provider, Web Parts connection.

constraint

See other term: generic type parameter constraint

constructed generic type

A generic type whose generic type parameters have been specified. A constructed type or method can be an open generic type if some of its type arguments are type parameters of enclosing types or methods, or a closed generic type if all of its type arguments are real types. See also: closed generic type, generics, generic type, generic type argument, generic type parameter, open generic type.

constructed type

See other term: constructed generic type

consumer

In a Web Parts connection, a server control that receives data from a provider control and processes or displays it. A consumer can be any type of server control, but must be designed to function as a consumer. A consumer must have a special callback method marked with a ConnectionConsumerAttribute attribute in the source code. This method receives data from the provider in the form of an interface instance. See also: connection point, provider, Web Parts connection.

container

See other term: naming container

container control

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

content control

A control that defines an area of a Microsoft Office Word document in which text and specific types of data can be displayed, or in which user input is restricted.

content page

In ASP.NET, a Web page that is configured to be merged with a master page to create a complete page. See also: master page.

context

An ordered sequence of properties that define an environment for the objects that resides 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. In the .NET Framework add-in programming model, a non-versioning interface that defines the methods and specifies the data types for transferring data over the communication pipeline between the host and the add-in. The contract is in the middle of the communication pipeline between the add-in and the host. The contract assembly is loaded into the application domains of both the add-in and the host. See also: add-in, host, pipeline.

control state

A field in an ASP.NET Web page that stores the current property settings for server controls on the page. Control state is used to recreate the page and reestablish previous settings on each postback. See also: ASP.NET page, ASP.NET server control, postback, view state.

cross-page posting

In ASP.NET Web pages, the process of submitting a page to a specified target page in contrast to submitting the page to itself. See also: postback.

CSDL

See other term: conceptual schema definition language

CTS

See other term: common type system

custom attribute (Attribute)

A class used to represent custom metadata. See also: attribute.

custom build rule

A build rule defined by the user, typically to call a tool that is not part of the normal Visual Studio build process.

custom control

Refrence:

 WWW.ZARSAZAN.IR

Of

MSDN 2008