Redgate software brings us a storyboard poster which explains .Net memory management in a simple and fun way!

"Variables" are simply storage locations for data becuase it is really hard to pragramme against the memory address. It means, a variable is just an association between a name and memory slot. You can place data into them and retrieve their contents as part of a C# expression. The size of ...

A new preview build of the upcoming free .Net decompiler from JetBrains, dotPeek, is available now. This latest build comes with all sorts of neat new features, and makes it usable as a part of your everyday toolbox.

Uncovering and correcting memory issues in managed applications can be difficult. Memory issues manifest themselves in different ways. For example, you may observe your application's memory usage growing unboundedly, eventually resulting in an Out Of Memory (OOM) exception. (Your application may eve...

In this post, Brian Rasmussen takes a look at how the Roslyn Scripting API can enable applications to evaluate code at runtime. While this has been possible since the dawn of .NET through the use of Reflection, Lightweight Code Generation, CodeDom, etc., it has never been particularly easy. All of t...

Igor Ostrovsky demonstrates the improvements that have been made to Parallel Extensions in the .NET Framework 4.5, and shows how you can use PLINQ queries to good effect.

Abhishek Goenka gives a short introduction to the .NET Framework's SecureString class which stores strings in memory in an encrypted form so that the data contained in the strings in memory cannot easily be ready from outside the application.

We've seen a few articles lately on ensuring that your memory is properly cleaned up during garbage collection, but today Michael McLaughlin comes in with tips to avoid automatic collection of your objects. Generally speaking, this is for performance reasons. Garbage collection in .Net 4 and earlier...

IDisposable is a standard interface in the .NET framework. This article discusses the importance of using it in parallel or multithread programming.

John Robbins walks us through debugging an application which is not clearing its memory during garbage collection due to WeakReferences. He shows us how to use the tools available to us to trace the memory problem all the way back to the source.

Following up an earlier article this week, Sam Saffron of Stackoverflow expands on how they mitigated performance problems caused by the .Net generational garbage collector.

S. Somasegar discusses several new features and improved functionality available in the .NET 4.5 Developer Preview. Performance among other things has seen a significant boost in .NET 4.5.

Well-known .NET developer Marc Gravell details how he eliminated some performance problems through clever use of structures, and explains how the CLR garbage collector behaves.

Surupa Biswas and Maoni Stephens from the Garbage Collection Feature Team at Microsoft share with us some improvements to memory allocation in .Net 4.5, specifically relating to large object allocation. Improvements have been made to how fragmented memory is allocated and used on the heap, as well a...