📑 Table of Contents▼

Managed code is computer program code that requires and will execute only under the management of a Common Language Infrastructure (CLI); Virtual Execution System (VES); virtual machine, e.g. .NET, CoreFX, or .NET Framework; Common Language Runtime (CLR); or Mono. The term was coined by Microsoft.

Managed code is the compiler output of source code written in one of over twenty high-level programming languages, including C#, J# and Visual Basic .NET.

Terminology

edit

The true and fine distinction between managed and unmanaged code is prevalent and only relevant when developing applications that interact with CLR implementations. Since many older programming languages (list) have been ported to the CLR, the differentiation is needed to identify managed code, especially in a mixed setup. In this context, code that does not rely on the CLR is termed "unmanaged".

A source of confusion was created when Microsoft started connecting the .NET Framework with C++, and the choice of how to name the Managed Extensions for C++. It was first named Managed C++ and then renamed to C++/CLI. The creator of the C++ programming language and member of the C++ standards committee, Bjarne Stroustrup, even commented on this issue, "On the difficult and controversial question of what the CLI binding/extensions to C++ is to be called, I prefer C++/CLI as a shorthand for 'The CLI extensions to ISO C++'. Keeping C++ as part of the name reminds people what is the base language and will help keep C++ a proper subset of C++ with the C++/CLI extensions."[1]

Uses

edit

The Microsoft Visual C++ compiler can produce both managed code, running under CLR, or unmanaged binaries, running directly on Windows.[2]

Benefits of using managed code include programmer convenience (by increasing the level of abstraction, creating smaller models) and enhanced security guarantees, depending on the platform (including the VM implementation). There are many historical examples of code running on virtual machines, such as the language UCSD Pascal using p-code, and the operating system Inferno from Bell Labs using the Dis virtual machine. Java popularized this approach with its bytecode executed by the Java virtual machine.

Google also mentions that Java and Kotlin are managed code in their Android NDK JNI documents. [3][4]

References

edit
  1. ^ Stroustrup, Bjarne (2009-06-29). "Bjarne Stroustrup's FAQ: What do you think of C++/CLI?". Retrieved 2009-06-29.
  2. ^ Gregory, Kate (2003-04-28). "Managed, Unmanaged, Native: What Kind of Code Is This?". Retrieved 2009-04-22.
  3. ^ "JNI tips | Android NDK". Android Developers. Retrieved 2020-06-21.
  4. ^ "Getting started with C++ and Android Native Activities".
edit

📚 Artikel Terkait di Wikipedia

Code injection

attacks. Some approaches that are used to detect and isolate managed and unmanaged code injections are: Runtime image hash validation, which involves capturing

Managed Extensions for C++

Managed and unmanaged code can be mixed together in the same CLI assembly seamlessly. This allows the programmer to keep unmanaged code that cannot be

Mono (software)

safety. Other .NET or Mono applications can use legacy code, which is referred to as unmanaged, by using the System.Runtime.InteropServices libraries

Blittable types

that have an identical presentation in memory for both managed and unmanaged code. Understanding the difference between blittable and non-blittable types

Platform Invocation Services

operating system libraries normally written in unmanaged code or third party libraries also written in unmanaged code. P/Invoke is the technique a programmer

Locale (computer software)

specific language and territory strings. The locale identifier (LCID) for unmanaged code on Microsoft Windows is a number such as 1033 for English (United States)

Machine code

ISBN 978-93-325-7040-5. Gregory, Kate (2003-04-28). "Managed, Unmanaged, Native: What Kind of Code Is This?". Developer.com. Archived from the original on 2009-09-23

Comparison of C Sharp and Java

that otherwise would require calling out to unmanaged code. An assembly (program or library) using unsafe code must be compiled with a special switch and