implicit-typing

In the simplified code below, if(city == "New York City") { var MyObject = from x in MyEFTable where x.CostOfLiving == "VERY HIGH" select x.*; } else { var MyObject = from x in MyEFTable where x.CostOfLiving == "MODERATE" select x.*; } foreach (var item in MyObject) { Console.WriteLine("<item's details>"); } The variable MyObject is not accessible outside conditional block. How can I iterate outside the if..else ? Let's clarify your confusing question. The problem is that you have two local variables, each of which has the same "unspeakable" type -- a sequence of anonymous type. I would change

This question already has an answer here: Implicit typing; why just local variables? 6 answers Why is it not possible to have implicitly-typed variables at a class level within C# for when these variables are immediately assigned? ie: public class TheClass { private var aList = new List<string>(); } Is it just something that hasn't been implemented or is there a conceptual/technical reason for why it hasn't been done? Here's a blog post from Eric that explains the reasoning. 来源： https://stackoverflow.com/questions/2771485/var-in-c-sharp-why-cant-it-be-used-as-a-member-variable

This question already has an answer here: Why would var be a bad thing? 17 answers I just installed a trial version of ReSharper and one of the first things I noticed is that it always suggests to replace explicitly typed local variables with implicitly typed ones, e.g: public string SomeMethod(int aParam) { int aNumber = SomeOtherMethod(aParam); // should be changed to: var aNumber = SomeOtherMethod(aParam); } I think explicitly typed variables are more readable (more explicit). What do you think about ReSharper's suggestion? Is there any advantage in using implicitly typed variables? When do

I've been chatting with my colleagues the other day and heard that their coding standard explicitly forbids them to use the var keyword in C#. They had no idea why it was so and I've always found implicit declaration to be incredibly useful when coding. I've never had any problems finding out what type the variable was (you only hover over the variable in VS and you'll get the type that way). Does anyone know why it would be a bad idea to use the var keyword in C#? The writers of the .Net Framework Design Guidelines (awesome book) that came out in November 2008 recommend considering using var

Why can't I use the array initializer with an implicitly typed variable? string[] words = { "apple", "strawberry", "grape" }; // legal string[] words = new string[]{ "apple", "strawberry", "grape" }; // legal var words = new []{ "apple", "strawberry", "grape" }; // legal var words = new string[]{ "apple", "strawberry", "grape" }; // legal var words = { "apple", "strawberry", "grape", "peach" }; // ILLEGAL Is there a technical reason for this limitation? Why can't it infer the type like it would for: var number = 10; var text = "Hello"; The compiler clearly knows what I am trying to do, it just