Why Should Application Developers Care about Managed Code?
Code that runs within the CLR is called managed code. Code that runs in the native OS and not the CLR, such as client libraries, COM components, etc. is called unmanaged code. You can mix managed and unmanaged code within a single application. Unlike 100% managed code, unmanaged code reaches outside the CLR, increasing complexity, reducing performance and opening potential security risks. While some vendors promote their .NET data providers as “built with managed code”, they do not promote the fact that the data provider must call to the client libraries to make a connection to the database, introducing unmanaged code. The following figure shows the difference between using a managed data provider that calls the client library and using a Wire Protocol managed data provider that connects to the DBMS with no intervening unmanaged code.
Related Questions
- Describe the advantages of writing a managed code application instead of unmanaged one. What’s involved in certain piece of code being managed?
- Describe the advantages of writing a managed code application instead of unmanaged one. Whats involved in certain piece of code being managed?
- Is XNA Game Studio 4.0 a completely managed code platform or can developers use native code?
