A

  • 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 

  • access control list (ACL)
    A list that specifies the rules for access to a particular resource. Microsoft Windows NT implements user-based ACLs, which specify the resources available to a particular user.
  • ADO.NET
    The suite of data access technologies included in the .NET Framework class libraries that provide access to relational data and XML. ADO.NET consists of classes that make up the DataSet (such as tables, rows, columns, relations, and so on), .NET Framework data providers, and custom type definitions (such as SqlTypes for SQL Server).
  • application base
    The directory where the .exe file that loads into the initial or default application domain is located. If you create your own application domain, the application base is the location you specify in the AppDomainSetup class. See also: application domain.
  • application domain (AppDomain)
    A boundary that the common language runtime establishes around objects created within the same application scope (that is, anywhere along the sequence of object activations beginning with the application entry point). Application domains help isolate objects created in one application from those created in other applications so that run-time behavior is predictable. Multiple application domains can exist in a single process.
  • ASP.NET
    A set of technologies in the Microsoft .NET Framework for building Web applications and XML Web services. ASP.NET pages execute on the server and generate markup (such as HTML, WML, or XML) that is sent to a desktop or mobile browser. ASP.NET pages use a compiled, event-driven programming model that improves performance and enables the separation of application logic and user interface. ASP.NET pages and XML Web services files created using ASP.NET contain server-side (rather than client-side) logic written in Visual Basic .NET, C# .NET, or any .NET-compatible language. Web applications and XML Web services take advantage of the features of the common language runtime, such as type safety, inheritance, language interoperability, versioning, and integrated security.
  • ASP.NET mobile controls
    A set of ASP.NET controls designed for mobile Web applications. ASP.NET mobile controls extend their ASP.NET server control counterparts.
  • ASP.NET mobile Web Forms
    Extensions to ASP.NET Web Forms that target mobile devices from cell phones to Pocket PCs.
  • ASP.NET page
    A component of an ASP.NET application.
  • ASP.NET server control
    A server-side component that encapsulates user-interface and related functionality. An ASP.NET server control derives directly or indirectly from the System.Web.UI.Control class. The superset of ASP.NET server controls includes Web server controls, HTML server controls, and ASP.NET mobile controls. The page syntax for an ASP.NET server control includes a runat="server" attribute on the control's tag. See also: HTML server control, validation server controls, Web server control.
  • ASP.NET Web application
    An application that processes HTTP requests (Web requests) and executes on top ASP.NET. An ASP.NET Web application can include ASP.NET pages, XML Web services, HTTP handlers, and HTTP modules.
  • assembly
    A collection of one or more files that are versioned and deployed as a unit. An assembly is the primary building block of a .NET Framework application. All managed types and resources are contained within an assembly and are marked either as accessible only within the assembly or as accessible from code in other assemblies. Assemblies also play a key role in security. The code access security system uses information about the assembly to determine the set of permissions that code in the assembly is granted. See also: private assembly, shared assembly.
  • assembly cache
    A code cache used for side-by-side storage of assemblies. There are two parts to the cache: the global assembly cache contains assemblies that are explicitly installed to be shared among many applications on the computer; the download cache stores code downloaded from Internet or intranet sites, isolated to the application that caused the download so that code downloaded on behalf of one application or page does not impact other applications. See also: global assembly cache.
  • assembly manifest
    An integral part of every assembly that renders the assembly self-describing. The assembly manifest contains the assembly's metadata. The manifest establishes the assembly identity, specifies the files that make up the assembly implementation, specifies the types and resources that make up the assembly, itemizes the compile-time dependencies on other assemblies, and specifies the set of permissions required for the assembly to run properly. This information is used at run time to resolve references, enforce version binding policy, and validate the integrity of loaded assemblies. The self-describing nature of assemblies also helps makes zero-impact install and XCOPY deployment feasible. See also: assembly, metadata.
  • assembly metadata
    See definition for assembly manifest.
  • assertion (Assert)
    In .NET Framework security, helps to make sure that a method has access to a particular resource even if the method's callers do not have the required permission. During a stack walk, if a stack frame asserting the required permission is encountered, a security check for that permission will succeed. Assertions can create security holes and should be used only with extreme caution.
  • attribute
    A descriptive declaration that annotates programming elements such as types, fields, methods, and properties. Attributes are saved with the metadata of a .NET Framework file and can be used to describe code to the common language runtime or to affect application behavior at run time.
  • authentication
    In .NET Framework security, the process of discovering and verifying the identity of a principal by examining the user's credentials against some authority. See also: principal.
  • authorization
    In .NET Framework security, the process of limiting access rights by granting or denying specific permissions to an authenticated identity or principal. See also: authentication, principal.