Friday, September 10, 2010

Value Types and Reference Types Explained

There are two types of data types in the .NET framework: Value and reference types.
Lets first have a look at the value types:

  1. Value types are allocated on the current thread’s stack.
  2. The lifetime of the value type is only inside the scope where it is used.
  3. When you pass a value type as a parameter in a method, the value type is copied.
  4. A wrapper object is created if you pass a value type to a method that expects an object.

Value types are suitable for representing lightweight objects such as vectors, matrices and colors. Value types has less overhead than classes by the fact that no additional memory for the reference is needed. However, there are a few things that are worth mentioning:

  • Structs can’t have a default parameterless constructor. It is provided by default and it initializes all the fields to their default values.
  • You can’t initialize an instance field inside a struct
  • You can’t use inheritance in structs

Value types are important for performance since they are allocated on the stack (the stack is not garbage collected) – they are cheaper to allocate and deallocate than classes. However, if your struct is more than 16 bytes, it may be more efficient to use a class instead.

Now, let us have a look at reference types:

  1. Stored on the managed heap.
  2. Variables that are reference types only contain a pointer to the data.
  3. Reference types are garbage collected when they are no longer referenced.
  4. Are always passed by reference (the pointer to the data is passed)

For your convenience, here is a list of value and reference types:

Value types Reference types

Boolean, Date and Char
Byte, Short, Integer, Long
Single and Double



The ref keyword

The ref keyword is very important when it comes to both performance and the behavior of value and reference types. If you put ref in front of a parameter in a method, the argument is passed by reference regardless whether it is a value or reference type.



The output of this application is “”. If we didn’t have the ref keyword in front of the parameter, the output would be “”. This is because the original pointer (reference) to the data is passed to the method when using the ref keyword. Value types can also be passed to the method by reference (and no, it does not get boxed) – yielding the same behavior as the reference type.

Tuesday, September 7, 2010

Blank Visual Studio 2010 Team Explorer Window

Recently I decided to upgrade my Visual Studio 2008 installation to Visual Studio 2010. I uninstalled all VS2008 packages and made sure to clean out folders left behind. After a long VS2010 installation I fired up Team Explorer and connected to my projects; after doing so, I was met by an empty Team Explorer window.

Several reinstalls later and registry changes I tried reading up on how to repair installations and came across the command:

devenv /setup

The setup switch did the trick and I now have a fully working Team Explorer window.