This documentation is archived and is not being maintained.
- managed code
- Code that is executed by the common language runtime environment rather than directly by the operating system. Managed code applications gain common language runtime services such as automatic garbage collection, runtime type checking and security support, and so on. These services help provide uniform platform- and language-independent behavior of managed-code applications. See also: unmanaged code.
- managed data
- Objects whose lifetimes are managed by the common language runtime. The runtime automatically handles object layout and manages references to these objects, releasing them when they are no longer being used. See also: common language runtime.
- Managed Extensions for C++
- A set of language extensions to C++ that help Visual C++ developers write .NET Framework applications. Managed Extensions allow you to mix unmanaged and managed C++ code within the same application.
- See definition for assembly manifest.
- Information that describes every element managed by the common language runtime: an assembly, loadable file, type, method, and so on. This can include information required for debugging and garbage collection, as well as security attributes, marshaling data, extended class and member definitions, version binding, and other information required by the runtime.
- Microsoft intermediate language (MSIL)
- A language used as the output of a number of compilers and as the input to a just-in-time (JIT) compiler. The common language runtime includes a JIT compiler for converting MSIL to native code. See also: JIT compilation.
- mobile user control
- An ASP.NET mobile control derived from the System.Web.UI.MobileControls.MobileUserControl class. User controls provide containers for custom controls built from other ASP.NET mobile controls. See also: ASP.NET mobile controls.
- A loadable unit, which can contain type declarations and type implementations. The module contains enough information to enable the common language runtime to locate all implementation bits when the module is loaded. The format for modules is an extension of the Windows portable executable (PE) file format. When deployed, a module is always contained in an assembly. See also: assembly, portable executable (PE) file.
- See definition for Microsoft intermediate language.