.NET Framework
|
The .NET Framework is a platform for building the next generation of distributed XML Web services and applications. It exposes a language-independent yet consistent programming model across all tiers of an application, while providing seamless interoperability with and easy migration from existing technologies. The .NET Framework consists of three things: the common language runtime, unified classes, and ASP.NET.
|
ADO.NET
|
Data access technology for the .NET Framework based on ActiveX Data Objects (ADO).
|
ASP.NET
|
Active Server Pages technology for the .NET Framework.
|
Assembly
|
The unit of deployment and versioning in the .NET Framework. It establishes the namespace for resolving requests and determines which resources are exposed externally and which are accessible from within the assembly. An assembly includes an assembly manifest, which describes the contents of the assembly
|
C#
|
The first component-oriented language in the C/C++ family. Submitted to ECMA for standardization.
|
CGI
|
Common Gateway Interface. An early Internet protocol used to generate interactive content over the Web.
|
Common Language Runtime (CLR)
|
The type, metadata, and execution systems provided by the .NET Framework. The CLR supplies managed code and data with services such as cross-language integration, code access security, object lifetime management, and debugging and profiling support. By targeting the CLR, compilers and other tools can offer these services to developers.
|
Common Language Specification (CLS)
|
A subset of .NET Framework features that are supported by a broad set of compliant languages and tools. CLS-compliant languages and tools are guaranteed to interoperate with other CLS-compliant languages and tools. For example, the type Int32 is CLS compliant, and languages and tools may expect that other CLS languages and tools know how to correctly use this type.
|
Disco
|
SOAP Discovery (Disco). Based on the SOAP Discovery specification. Disco provides a set of rules for discovery of Web services descriptions and capabilities.
|
ECMA
|
A European standards body created in 1961. Internationally accredited ECMA has fast-track approval for ISO and is the forum for successful standards such as ECMAScript.
|
Evidence-based Security
|
The .NET Framework introduces the concept of evidence-based security, referring to inputs to the security policy about code—such as from what site, security zone, or URL was an assembly obtained, what is its strong name, and whether it has a digital signature and from whom. Based on these and other answers, the appropriate security policy can be applied, and the appropriate permissions may be granted to the assembly. Answers can come from multiple sources, including the CLR, the browser, ASP.NET, and the shell, depending on the source of the code.
|
Garbage Collection
|
The process of transitively tracing through all pointers to actively used objects to locate all objects that can be referenced and then arranging to reuse any heap memory that was not found during this trace. The CLR’s garbage collector also arranges to compact the memory that is in use to reduce the working space needed for the heap.
|
HTTP
|
Hyper Text Transfer Protocol is a standard Internet protocol for transfer of information between servers and between clients and servers.
|
IDL
|
Interface Definition Language. A language used by applications to specify the various interfaces they intend to offer to other applications.
|
Intermediate Language (IL)
|
Intermediate Language (IL). A language used as the output of a number of compilers and as the input to a JIT compiler. IL defines an abstract, stack-based execution architecture. The CLR may include several JIT compilers for converting IL to native code.
|
JIT
|
Just-in-Time. A phrase that describes an action that is taken only when it becomes necessary, such as just-in-time compilation or just-in-time object activation. By convention, the term JIT alone is used to refer to a JIT compiler.
|
Loosely Coupled Architecture
|
A distributed application in which you can change the implementation of one tier without affecting any of the other tiers. Contrast tightly coupled architecture.
|
Managed Code
|
Managed code supplies the metadata necessary for the CLR to provide services, such as memory management, cross-language integration, code access security, and automatic lifetime control of objects. All code based on IL executes as managed code.
|
Manifest
|
Metadata describing which modules and resource files are part of a particular assembly, which types are exported, and which other assemblies are referenced. It also specifies which security permissions are required to run, what additional permissions are optionally requested, and what permissions the assembly refuses.
|
Metadata
|
Data (or information) about data. In the CLR, metadata is used to describe assemblies and types. It is stored with them in the executable files, and is used by compilers, tools, and the runtime to provide a wide range of services. Metadata is essential for runtime type information and dynamic method invocation. Many systems use metadata—for example, Type Libraries in COM provide metadata
|
Native Code
|
Code that has been compiled to processor-specific machine code.
|
n-tier
|
System architecture that separates presentation, business logic, data access, and database (or other persistence mechanism) tiers.
|
Reflection
|
.NET Framework technology that allows you to examine metadata that describes types and their members.
|
SOAP
|
Simple Object Access Protocol, WC3 standard. A lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML-based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses.
|
Tightly Coupled Architecture
|
A distributed application where a change to any tier affects some or all the other remaining tiers. Contrast loosely coupled architecture.
|
UDDI
|
The Universal Description, Discovery, and Integration [UDDI] specification. An initiative that creates a global, platform-independent, open framework to enable businesses to discover each other, define how they interact over the Internet, and share information in a global registry
|
Unified Classes
|
The .NET Framework’s unified, object-oriented, hierarchical, and extensible set of class libraries (APIs) that developers can use from the languages they are already familiar with.
|
Unmanaged Code
|
Code that was created without knowledge for the conventions and requirements of the .NET Framework. Unmanaged code executes in the .NET Framework environment with minimal services (for example, no garbage collection, limited debugging , no declarative security). Unmanaged code does not have self-describing metadata.
|
Web API
|
Application programming interfaces (APIs) that enable integration of an XML Web service under the .NET Framework.
|
Web Forms
|
Web Forms are an ASP.NET technology that you use to create programmable Web pages. They can present information, using any markup language, to the user in any browser and use code on the server to implement application logic.
|
WebMethod
|
Programming keyword in .NET Framework that enables objects to be Internet accessible.
|
Windows Forms
|
The Windows Forms framework encapsulates native Win32 APIs and exposes secure, managed classes for creating Win32 client-side applications. The Windows Forms class library provides many controls, such as buttons, check boxes, drop-down lists, combo boxes, data grid, and others, that encapsulate user-interface and other client-side functionality.
|
WSDL
|
Web Services Description Language. An XML grammar that developers and development tools use to represent the capabilities of an XML Web service.
|
XML
|
Extensible Markup Language. WC3 standard for the format of structured documents and data on the Web.
|
XML Web Service
|
An XML Web service is an application that exposes its functionality programmatically over the Internet or intranets using standard Internet protocols and standards, such as HTTP and XML.
|