Amen!

That suggestion is so annoying, think the first thing I did was turn that suggestion off when I installed one of the first EAPs a while back.

To uninstall ReSharper and lose so much just because of one annoyance is a bit extreme.  

If I was that dogmatic about all software, I would ever touch a keyboard!

I went the opposite direction. I have ReSharper converting everything it can to var automatically during a (Ctrl-Shift-Alt-F) code format. I love it.

Incidentally, when you see the hint "squiggly" for this (or any) rule, you can press Alt-Enter, select Inspection Options, and alter the "severity" of the rule right then and there.

Didn't anyone notice that you can turn off this "var" rule by setting solution "Language Level" property to "C# 2.0"? The default value is C# 3.0 which automatically turns on the var rule.

Kyle: So you prefer var instead of the "real" type? Why is that?

At least that one is easy to turn off, I still haven't found out how to stop every delegete from being wrapped inside its own nested type region.

Lex Y. Li: I am sure everyone does realise that, but it has the disadvantage of marking all other c# 3 features as errors, and no real advantage over simply adjusting the specific setting.

Oh and I currently have my settings adjusted to use the var, but only where the default setting does it, on the same line as newing a constructor, so the type is there anyway.

I think its growing on me, looks silly now to have the type written twice on the same line, redundant somehow. (Well after working a bit in python lately, even the var itself is starting to look a little redundant.)

One of the (few) worst things about c# is the amount of boiler-plate so anything that reduces that is ok with me.

Now if only resharper could convert everything into lambda expressions, I could truly out-guru my colleges.

@mikael

I commented when JP posted on it over here: codebetter.com/.../got-var.aspx

The short version is: Most of the time, I can either glean the type easily (when combined with a new statement or by appropriate naming) or I don't care what specific type it is (e.g. IList vs. IEnumerable vs. my own implementation).

I know a lot of people don't like it but it works for me. That said, I won't defend my position to the death. If I'm on a team that prefers not to use it, I'll bow to the majority without much fuss.

I'd prefer it simply kept var off.  Since I can't even pass an inferred type around to other methods it doesn't provide much help.