The process or method for configuring controls on a form or Web page to fetch data from or write data to a data source such as a database, XML file, and so on.
data source control
An object that can be added to an ASP.NET Web page that encapsulates the logic required to connect to a data source, such as a database or XML file, and that can execute queries or other data-access commands. A data source control can in turn provide data to other controls on that page.
In multithreading, a condition in which each of two threads holds a lock that the other thread needs in order to proceed. See also: synchronization.
A group of one or more cards. See also: card.
declarative security check
Declarative security information in metadata. Developers can use such declarations, which are usually written as custom attributes, to invoke several kinds of security functionality: require permissions to bind reference to the code, require permissions to derive a type, demand that callers have certain permissions, and so on. See also: imperative security check.
A provider hosted in a separate process from WMI. Decoupled providers are the recommended way to instrument an application because the provider can control its own lifetime instead of being launched every time a user accesses the provider through WMI. See also: provider.
default unit system
The process that determines when a Web page control should appear on a new page, based on a mobile device's characteristics. The default unit system is based on one line equaling 100 units, as indicated by the DefaultWeight field in the ControlPager class.
In the .NET Framework, a reference to a function. A delegate is equivalent to a function pointer.
In WMI, a security impersonation level used to allow remote access involving more than one network hop.
A filter that uses a custom method to evaluate the specified data.
By denying a permission, a method can prevent its callers from exercising the privilege represented by that permission. If a method on the call stack denies permission A, a stack walk checking for permission A will fail unless a valid assertion is found on the stack between the method doing the denial and the method that initiated the check for permission A. See also: assertion.
denial of service attack
An attack on a server exposed to the Internet that consumes excessive time, memory, or other resources. The attack intends to prevent rightful access to resources.
The file used in ClickOnce applications that describes the current version of this deployment, and whether it should be installed on the client computer or only run online.
An ASP.NET page framework class that adapts the behavior of mobile pages and controls based on the target device.
The set of device functionality available through the HasCapability method or the <Choice> element.
The coordinates used by the physical device being drawn on, such as a screen or sheet of paper.
The characteristics of a device available through the MobileCapabilitiesclass and the DeviceSpecific control.
A section of the Web.config file where you specify values for specific mobile devices. These values are used to create device-specific content.
A way of accessing properties and methods supplied by WMI in a script as if they were automation properties and methods of an object instance.
The different display states that a Web Parts page can enter, which enable users to modify a page in specified ways. The states that ship with the Web Parts control set are: catalog, connect, design, edit, and browse. The default or normal mode for a Web page is browse. Developers can extend this display mode feature by adding custom display modes, which requires extending the WebPartManager class. See also: Web Parts control set, Web Parts page.
The way of determining which control borders are set flush with their parent control and how a control is resized with its parent. Docking and anchoring are mutually exclusive. See also: anchoring.
See definition for assembly cache.
A Web Parts control that is persisted in a personalization store; it does not appear in the declarative markup of an .aspx page. After it has been added to a page, the WebPartManager control automatically creates an instance of the control from the personalization store on future requests. See also: Web Parts controls.