Introduction
The .NET CLR provides a common context within which all .NET applications execute, regardless of teh language in which they are written.CLR is responsible for handling every aspects of the managed code such as memory and resource management, secure environment to run in, garbage collection , access to the operating systems services etc. Code that targets the CLR is commonly known as managed code Read more »
VN:F [1.7.2_963]
Rating: 5.0/5 (1 vote cast)
C# general
|
.Net, CLR, Code Execution, Compiling MSIL, Execution, Garbage Collection, interoperability, JIT, Just-in-Tim, Managed Code, Managed Execution Process, MSIL, resource management
Of all of the technologies to be found in .NET, the most controversial, seems to be garbage collection. A key part of the .NET framework, the managed heap and the garbage collection mechanism are foreign ideas to many of us. This installment of my .NET column discusses the managed heap, and how you can take advantage of it.
Why a Managed Heap?
The .NET framework includes a managed heap that all .NET languages use when allocating reference type objects. Lightweight objects known as value types are always allocated on the stack, but all instances of classes and arrays are created from a pool of memory known as the managed heap. Read more »
VN:F [1.7.2_963]
Rating: 5.0/5 (1 vote cast)
Introduction
DotNet developers can free themselves from tedious memory management for their application as Microsoft Framework and CLR do it automatically.CLR provides a mechanism called as Garbage Collection which manages your applications memory. In this session we will discuss how garbage collector works and how it affects the performance of your Applications.
When you create an object using new () operator, the object’s memory is obtained from the managed heap. When the garbage collector decides that sufficient garbage has accumulated, it performs a collection to free some memory. This process is fully automatic, but there are a number of factors that you need to be aware of that can make the process more or less efficient. Read more »
VN:F [1.7.2_963]
Rating: 4.5/5 (2 votes cast)
Best Practices, C# general, System Analysis and Design
|
.Net, Dispose, Finalization, Garbage Collection, Garbage Collection Algorithm, Generations, Implement Dispose method, Performance, System.GC
Introduction
This article is about understanding the working concept of destructor in C#. I know you all may be thinking why a dedicated article on simple destructor phenomenon. As you read this article you will understand how different is C# destructor are when compared to C++ destructors.
In simple terms a destructor is a member that implements the actions required to destruct an instance of a class. The destructors enable the runtime system, to recover the heap space, to terminate file I/O that is associated with the removed class instance, or to perform both operations. For better understanding purpose I will compare C++ destructors with C# destructors. Read more »
VN:F [1.7.2_963]
Rating: 3.0/5 (1 vote cast)
Introduction
Garbage collection is a process of releasing the memory used by the objects, which are no longer referenced. This is done in different ways and different manners in various platforms and languages. We will see how garbage collection is being done in .NET.
Read more »
VN:F [1.7.2_963]
Rating: 3.0/5 (1 vote cast)