A specific version policy that requests a given assembly be run with the exact version of its dependencies that it was compiled against.
A .NET Framework assembly containing resources specific to a given language. Using satellite assemblies, you can place the resources for different languages in different assemblies, and the correct assembly is loaded into memory only if the user elects to view the application in that language.
In WMI, a collection of class definitions that describe managed objects in a specific environment.
A data structure that contains the security information for a securable object, such as a share, file, sink, or event filter. A security descriptor identifies the object's owner and primary group. It also identifies who can have access to the resource and what type of access.
An unintentionally unprotected entry point into an otherwise restricted computer, component, application, or other online resource.
security identifier (SID)
A data structure that identifies user, group, and computer accounts. Every account on a network is issued a unique SID when the account is first created. SIDs are used in access control (the process of comparing a SID to a resource security descriptor that specifies which SIDs can use the resource).
The active policy established by the administrator that programmatically generates granted permissions for all managed code based on the code's requested permissions. Code that requires more permissions than policy will grant is not allowed to run. See also: requested permissions.
A WMI Query Language statement that is used to retrieve information. SQL supports queries across multiple tables, but WQL supports only single class queries. See also: ASSOCIATORS OF, GROUP, HAVING, ISA, REFERENCES OF, WHERE, WITHIN.
A method call that returns immediately and allows the application or script to enumerate the returned objects as a collection. A semisynchronous method call does not require setting up an object sink, but an asynchronous method call does require setting up an object sink. See also: asynchronous method.
The process of converting an object's state information into a form that can be stored or transported. During serialization, an object writes its current state to temporary or persistent storage. Later, the object can be recreated by reading, or deserializing, the object's state from storage.
See definition for ASP.NET server control.
In ASP.NET, a variable store created on the server for the current user; each user maintains a separate Session state on the server. Session state is typically used to store user-specific information between postbacks. See also: postback.
An assembly that can be referenced by more than one application. An assembly must be explicitly built to be shared by giving it a cryptographically strong name. See also: assembly, private assembly, strong name.
A Web Parts control that can appear on a Web page and be personalized when the page is in either shared or user-level personalization scope. Note that a shared control can have properties that are both user-scope and shared-scope for personalization purposes. See also: personalization, personalization scope, Web Parts controls.
See definition for strong name.
See definition for security identifier.
The ability to install and use multiple versions of an assembly in isolation at the same time. Side-by-side execution can apply to applications and components as well as to the .NET Framework. Allowing assemblies to coexist and to execute simultaneously on the same computer is essential to support robust versioning in the common language runtime.
The list of types involved in the definition of a method, field, property, or local variable. For a method, the signature includes its name, number of parameters and their types, the type it returns (if any), and its calling convention (default or vararg). The signature for a property is similar to that of a method. The signature for fields and local variables is simply their type (for example, array [0..5] of int).
A file or other store that describes the logical layout of a Web site (as distinct from the physical layout of pages). Sitemaps are used by site navigation controls to display navigation using a menu, tree view, or SiteMapPath (breadcrumb) control. See also: site navigation.
In ASP.NET Web sites, the process of displaying controls such as menus, a tree view, or SiteMapPath (breadcrumb) controls that assist users in finding pages of interest. Site navigation is typically driven from a sitemap. See also: sitemap.
The process of changing the appearance of an image by changing the angles of the polygon the image is contained in.
A file containing one or more control properties that define how the control should look. Skin files are part of ASP.NET themes. See also: theme.
A glyph attached to a control or component that exposes commonly performed tasks.
Visual guides that the Windows Forms Designer draws to aid in the placement and alignment of controls.
A simple, XML-based protocol for exchanging structured and type information on the Web. The protocol contains no application or transport semantics, which makes it highly modular and extensible.
split stack layout
A layout style in which each end of the ToolStrip is the base of a stack, with some items stacked at the head and other items stacked at the tail. Items are stacked from the ends in.
A layout style in which adjacent items align against each other as though they were stacked, always taking up the free space in between the items.
In WMI, one of several preinstalled permanent consumers that perform an action, such as sending an e-mail or writing to a log when configured by a managed object format (MOF) file or a script. See also: permanent consumer.
A Web Parts control that is part of the declarative "page persistence" markup in an .aspx page; it exists only as part of the .aspx page, not in a personalization store like a dynamic Web Parts control. Unlike a dynamic control, a static control is added to an .aspx page on every request. A static Web Parts control is always a shared control, which means that although users can both personalize and "close" the control when the page is in either shared or user scope, the control can never be permanently deleted. See also: personalization, personalization scope, shared control, Web Parts controls.
The flow of data from a source to a single receiver that flows through a channel, as opposed to packets, which may be addressed and routed independently, possibly to multiple recipients.
The process of adjusting the size of an item to fit its container. The term "stretch" is typically used when referring to an image contained in a control.
A name that consists of an assembly's identity, its simple text name, version number, and culture information (if provided) strengthened by a public key and a digital signature generated over the assembly. Because the assembly manifest contains file hashes for all the files that constitute the assembly implementation, it is sufficient to generate the digital signature over just the one file in the assembly that contains the assembly manifest. Assemblies with the same strong name are expected to be identical. See also: assembly, assembly manifest.
A user-defined value type. Like a class, structures can contain constructors, constants, fields, methods, properties, indexers, operators, and nested types. Unlike classes, however, structures do not support inheritance. See also: class, field, indexer, nested type, property, value type.
In ClickOnce, a regularly-scheduled, automated check for application updates. Subscriptions are defined in the ClickOnce deployment manifest.
In multithreading, the coordination of the activities of multiple threads through locks and signaling mechanisms, so that program data is protected from corruption, and deadlocks and race conditions do not occur. See also: deadlock, race condition.
In WMI, a class that the CIM Object Manager defines to support core features such as event notification, security, and localization. A system class is automatically defined in each namespace. See also: CIM Object Manager.
In WMI, a property that the CIM Object Manager defines to provide information that applies to each class (for example, name, derivation, and namespace). See also: CIM Object Manager.