What are the differences between value types and reference types in C#? [duplicate]

Question

I know a few differences,

1. Value types are stored on the stack where as reference types are stored on the managed heap.
2. Value type variables directly contain their values where as reference variables holds only a reference to the location of the object that is created on the managed heap.

Is there any other difference i missed... If so,what are they?

Incorporeity

asked many times already on SO.... – Infidelity

@Wheat, Quickly searching, no, this question hasn't been asked or answered directly. – Aleksandrovsk

I don't have the time to answer this fully at the moment - but I'd just like to point out that "value types are stored on the stack" is an overstatement. See pobox.com/~skeet/csharp/memory.html. For more on reference types vs value types, see pobox.com/~skeet/csharp/references.html – Hypso

@Aleksandrovsk - The phrasing is slightly different but the topic is covered in a lot of places. For example #1130968 – Preamble

Value types can be stored on the heap when boxed msdn.microsoft.com/en-us/library/yz2be5wk.aspx – Quadruple

Answer 1

Please read: The stack is an implementation detail, and don't ever again repeat the canard that stack allocation is what differentiates value types from reference types in .NET. The CLR may choose to allocate a variable anywhere it wants to.

The most important difference is in the assignment semantics. When you assign a value type to a variable (or pass it to a method as an argument), all of the data is copied. When you assign a reference type, only a reference is copied - both references point to the same object instance in memory.

Agama

Bit harshly worded but hey that's the best way I learnt, like if you annoyed Gandalf and awaiting him explaining it to you with annoyance in his voice, it tends to stick =D – Kimura

Answer 2

Here are some additional differences:

1. Value types cannot be inherited, whereas reference types can
2. Value types are implemented as a struct, reference types as a class
3. Value types, by default, cannot be assigned real null values (the ? syntax is a workaround and still doesn't result in a true null value)
4. Assigning a value type to another variable, or passing it as a parameter in a method, makes a copy of it whereas with a reference type the variable represents the memory location of the object
5. It is a compile-time error for a struct to declare an explicit parameterless constructor, but the same does not apply to a class
6. It is a compile-time error to use the "this" object before all fields are assigned in a struct, but the same does not apply to a class
7. It is a compile-time error for a struct to not fully assign all properties in its constructor, but the same does not apply to a class

Quadruple

Answer 3

As mentioned by Aaronaught and Eric blog post:

Remember the rule, Reference types always goes to the Heap, whereas Value Types always go where they were declared? If a Value Type is declared outside of a method, but inside a Reference Type it will be placed within the Reference Type on the Heap.

Spite

Answer 4

i think values are implicitly assigned memory but not reference types they must be assigned memory explicitly

Rattoon