Why should I use var instead of a type?

c# .net coding-style resharper var
IAdapter picture IAdapter · Feb 1, 2011 · Viewed 125.6k times · Source

Possible Duplicate:
ReSharper and var

After I have installed ReSharper it demands(by warnings) that I use var whenever possible, for example

UnhandledExceptionEventArgs ue = (UnhandledExceptionEventArgs) t;

ReSharper wants to turn it into

var ue = (UnhandledExceptionEventArgs) t;

I like the first version better, is there any reason to prefer var? better performance? anything? or is it just a code style?

Answer

Martin Buberl picture Martin Buberl · Feb 1, 2011

It's really just a coding style. The compiler generates the exact same for both variants.

See also here for the performance question:

Related questions

Order of items in classes: Fields, Properties, Constructors, Methods

Is there an official C# guideline for the order of items in terms of class structure? Does it go: Public Fields Private Fields Properties Constructors Methods ? I'm curious if there is a hard and fast rule about the order of …

Read More
Does anyone still use [goto] in C# and if so why?

I was wondering whether anyone still uses the "goto" keyword syntax in C# and what possible reasons there are for doing so. I tend to view any statements that cause the reader to jump around the code as bad practice …

Read More
StyleCop XML Documentation Header - Using 3 /// instead of 2 //

I am using XML documentation headers on my c# files to pass the StyleCop rule SA1633. Currently, I have to use the 2 slash commenting rule to allow StyleCop to recognize the header. for example: // <copyright file="abc.ascx.cs" …

Read More