Export (0) Print
Expand All

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 

padding

The space between the edge of a control and a control’s contents. Padding differs from margin, which represents the space between controls on a form or page.

page coordinates

The coordinate system used by a drawing surface, such as a form or control.

pagination

A mechanism that automatically separates the content in ASP.NET mobile Web Forms into smaller groups of rendered pages that are targeted to fit a specific device. It also renders user interface elements that can be used to browse to other pages.

parameter constraint

See definition for generic parameter constraint.

parameterized type

A type whose definition has placeholders for actual types that the user specifies when creating and using instances of the type. C++ templates and common language runtime generics are examples of parameterized types. See also: generics.

parameterless constructor constraint

A restriction on a generic type parameter, such that types substituted for that type parameter must provide a parameterless or default constructor. See also: generics, generic type parameter constraint, generic type parameter.

part control

A control in the Web Parts control set that inherits directly or indirectly from the System.Web.UI.WebControls.WebParts.Part class and is used to create the primary user interface of Web Parts applications. See also: Web Parts control set.

PE file

See definition for portable executable (PE) file.

performance counter

A property in a performance class that stores performance data. The counter is a member of a performance object in the original performance library.

permanent consumer

In WMI, an event consumer whose registration lasts until it is explicitly cancelled. See also event consumer, temporary consumer.

permission class

A class that defines access to a resource or defines an identity by supporting authorization checks. See also: permission object.

permission object

An instance of a permission class that represents access rights to resources or identity. A permission object can be used to specify a request, a demand, or a grant of permission. See also: permission class.

personalization

A feature of the Web Parts control set that enables end users to personalize (modify) Web Parts controls and save the personalized settings. Personalization can apply to individual users (user scope) or to all users (shared scope). See also: Web Parts controls, Web Parts control set.

personalization scope

The state of a Web Parts page that determines the range of users to which personalization changes apply. The WebPartManager control determines the personalization scope for a Web Parts page. The PersonalizationScope enumeration provides two possible scopes (Shared and User) that a page can be in at any given time. In shared scope, personalization changes made to shared controls apply to all users. In user scope, personalization changes made to shared and per-user controls apply only to the specific user. See also: personalization, Web Parts page.

per-user control

A dynamic Web Parts control that can be personalized and permanently deleted from a page for an individual user only. A per-user control appears on the page only when the page is in user scope. Note that a per-user control can have properties that are both user-scope and shared-scope for personalization purposes. See also: personalization, Web Parts controls.

platform invoke

The functionality provided by the common language runtime to enable managed code to call unmanaged native DLL entry points.

portable executable (PE) file

The file format used for executable programs and for files to be linked together to form executable programs.

postback

The process in which a Web page sends data back to the same page on the server.

precompilation

In ASP.NET, the process of submitting an entire Web site to a compiler. The resulting Web site output runs without needing to be compiled on first request, and does not require source code to be deployed to a production server.

primary interop assembly

An assembly containing definitions of COM types that is distributed and digitally signed by the author of the COM component. Visual Studio uses a registered primary interop assembly by default when a developer references a type in the corresponding type library. See also: assembly, interop assembly.

principal

In .NET Framework security, represents the identity and role of a user, and acts on a user's behalf. See also: role.

private assembly

An assembly that is available only to clients in the same directory structure as the assembly. See also: assembly, shared assembly.

private view state

State information that is written as a hidden field, such as the form that is currently active or the pagination information for a form.

profile property

In ASP.NET, a property that can store information for each unique user and that is managed automatically by ASP.NET. When users visit the site, ASP.NET associates each user with a unique ID and can then read and write profile property values for the user.

property

In the .NET Framework, a class member that is like a public field, but that includes features such as versioning, encapsulation, and the ability to execute additional logic through get and set accessor methods. See also: encapsulation, field, version policy.

In WMI, a name/value pair that describes a unit of data for a class. Property values must have a valid Managed Object Format (MOF) data type.

provider

In a Web Parts connection, a server control that sends data to a consumer control. A provider can be a WebPart control or any type of server control, but must be designed to function as a provider. A provider must have a special callback method in the provider marked with a ConnectionProviderAttribute in the source code. This method provides data to consumer controls in the form of an interface instance. See also: connection point, consumer, Web Parts connection.

In WMI, a COM server that communicates with managed objects to access data and event notifications from a variety of sources, such as the system registry or an SNMP device. Providers forward this information to the CIM Object Manager for integration and interpretation. See also: CIM Object Manager.

Community Additions

ADD
Show:
© 2014 Microsoft