ADO .NET
A component of the Microsoft .NET Framework for providing dynamic access to data held in a database.
AppDomain—see Application Domain
Application Domain (AppDomain)
Known as a lightweight process. Prior to .NET, isolation was achieved through separate processes using the assistance of the OS and the supporting hardware. If one process was having problems it would not impact the entire machine, the impact would be isolated to just the involved process. Because types are tightly controlled with the .NET Framework, a mechanism exists to run several application domains (AppDomains) in a single process, the same level of isolation can occur within a single process, but without incurring the additional overhead of making cross-process calls or switching between processes.
ASP .NET
A component of the Microsoft .NET Framework for building, deploying and running Web applications and distributed applications.
assembly
The primary unit of deployment within the .NET Framework. Within the base class libraries is a class that encapsulates the features of an assembly, and is named Assembly. This class exists in the System namespace. An assembly can contain references to other assemblies and modules. Developers create a managed code assembly by combining their own application source code with code from the .NET class libraries.
common language runtime (CLR)
The core runtime engine in Microsoft .NET Framework for executing .NET applications. The CLR loads an application using the application's assembly manifest. The CLR locates the correct version of each assembly within an application. The CLR supplies managed code with services such as cross-language integration, code access security, object lifetime management, and debugging and profiling support.
CLR—see Common Language Runtime
COM+
An extension of Microsoft Component Object Model (COM) application programming environment. COM+ is Microsoft's strategic approach for developing applications using programmatic build block.COM+ is both an object-oriented programming architecture and a set of operating services.
config files
Configuration files such as the web.config, machine.config, and the global.config let an application's assembler or deployer customize their application using declaratives specified within one or more configuration files.
csc.exe
The C# (C Sharp) compiler.
Distributed Component Object Model (DCOM)
A set of Microsoft concepts and programmatic interfaces that facilitate communication between a client program object and a server program object. The server program object is distributed on a network-connected computer.
DCOM—see Distributed Component Object Model
GAC—see Global Assembly Cache
garbage collection
A .NET feature provided by the CLR. The CLR monitors the execution of the translated managed code and periodically releases memory when the application no longer has any valid reference to that memory. The process of garbage collection absolves the application developer from having to keep track of memory usage and explicitly request unused memory be returned to the system.
Global Assembly Cache (GAC)
A .NET Framework facility that lets assemblies be stored globally in a cache. The GAC lets .NET applications access assemblies without having an explicit reference in their own assemblies.
IIS—see Internet Information Server
IL—see Intermediate Language
instance
A term used to describe a particular instantiation of a programmatic abstraction of a template, such as a class, object, or a computer process.
Intermediate Language (IL)
The language in which assemblies are written. It is a set of instructions that represent the code of an application. It is considered to be "intermediate" because it is not code that is native for a particular processor. The intermediate code must be translated into a processor's native code. When the code that describes a method is required to run, it is compiled into native code with the Just-in-Time (JIT) compiler.
Internet Information Server (IIS)
A Microsoft product that provides a group of Internet servers including a Web or HTTP server, and an FTP server.
JIT—see Just-In-Time Compilation
Just-In-Time Compilation
A term that refers to the CLR's ability to defer the translation of an application's MSIL until the code is actually needed during execution.
managed code
A .NET term that refers to MSIL code that is loaded, translated, verified and executed by .NET's CLR. Managed code must supply the information necessary for the CLR to provide services such as memory management, cross-language integration, code access security, and automatic lifetime control of objects. All MSIL code executes as managed code.
Microsoft Intermediate Language (MSIL)
A CPU-independent instruction set that is generated by the .NET Framework compiler. Before MSIL can be executed it must be converted to native, CPU-specific code by the CLR.
module
A single file that contains executable content. An assembly can encapsulate one or more modules; a module does not stand-alone without an assembly referring to it. A class exists in the .NET base class library that encapsulates most of the features of a module. This class is called Module. The Module class exists in the System namespace.
MSIL—see Microsoft Intermediate Language
object
In object-oriented programming (OOP), objects are programmatic units that contain code and optionally data.
resgen.exe
A .NET utility that converts files from one resource format to another.
serialization
In .NET, serialization refers to the process of encoding an object, and the objects that are reachable from that object, into a byte stream. The byte stream represents an instantiated object and contains sufficient information to create a reconstruction of the object. The byte stream is suitable for transmitting over a network.
type
Within each computer language, a type is a definition from which values can be instantiated. The .NET's Common Type System (CTS) eliminates the need for each language to implement data types in its own unique and incompatible way. CTS understands two fundamental different types; Value types and Reference types. Types can have static, instance and virtual methods, and static and instance fields, events and properties.
type loader
The part of the .NET CLR that is responsible for loading the implementation of a class into memory, checking it for consistency, and preparing the class for execution.
unmanaged code
Code that is native to the processor and is executed directly by the operating system. Unmanaged code provides its own memory management, type checking, and security support. Interoperability features of the CLR let applications mix managed and unmanaged code. It is important to note that unmanaged code executes outside the control of the CLR and therefore an application is vulnerable to failures occurring in unmanaged code.
Windows Server 2008
A Microsoft multipurpose operating system capable of handling a wide range of server roles. Some server roles include; File and Print server, Web server, Application server, Mail server, Terminal server, Remote Access server, Virtual Private Network (VPN) server, Directory Service server, Domain Name System (DNS) server, Dynamic Host Configuration Protocol (DHCP) server, Streaming Media server, and Windows Internet Name Service (WINS) server.
xcopy deployment
The deployment of .NET assemblies can be accomplished by doing nothing more than xcopy'ing the application directories to a different path destination.
.NET Framework
A set of integrated components, provided as class libraries in a single, logically organized class hierarchy. The .NET Framework provides .NET application developers with the software they need to build code that executes under the control of NET's CLR. The .NET Framework provides an enormous collection of system support functions including technologies for Web services, and Web applications (ASP.NET), data access (ADO.NET), smart client applications (Windows Forms), file system and network access, XML functionality and many others.
|
Copyright © 2014 CA.
All rights reserved.
|
|