This is a new C# 6 feature, “Getter-only auto-properties”, also known as “Auto-Property Initializers for Read-Only Properties” as discussed in this MSDN magazine article ‘C# : The New and Improved C# 6.0’ by Mark Michaelis and in the C# 6.0 draft Language Specification. The read-only field’s setter is only accessible in the constructor, in all … Read more
In a new C# 6.0 we can define methods and properties using lambda expressions. No, you can’t. You can define method and property bodies using syntax which looks like a lambda expression, in that it uses the token =>. However, importantly this does not mean that there’s a delegate type involved. (Whereas a lambda expression … Read more
Update: C# 6.0 supports await in catch Old Answer: You can rewrite that code to move the await from the catch block using a flag: WebClient wc = new WebClient(); string result = null; bool downloadSucceeded; try { result = await wc.DownloadStringTaskAsync( new Uri( “http://badurl” ) ); downloadSucceeded = true; } catch { downloadSucceeded = … Read more
No, you can’t use string interpolation with something other than a string literal as the compiler creates a “regular” format string even when you use string interpolation. Because this: string name = “bar”; string result = $”{name}”; is compiled into this: string name = “bar”; string result = string.Format(“{0}”, name); the string in runtime must … Read more
Yes. The most important part is that the method containing lambda implementation is now an instance method. You can see a delegate as a middleman receiving an instance call through Invoke and dispatching that call according to the calling convention of the implementing method. Note that there are platform ABI requirements that specify how arguments … Read more
Yes. nameof() is evaluated at compile-time. Looking at the latest version of the specs: The nameof expression is a constant. In all cases, nameof(…) is evaluated at compile-time to produce a string. Its argument is not evaluated at runtime, and is considered unreachable code (however it does not emit an “unreachable code” warning). From nameof … Read more
It appears the syntax has slightly changed since those blog posts were written. As the error message suggests, add static to your include statement: using static System.Console; // ^ class Program { static void Main() { WriteLine(“Hello world!”); WriteLine(“Another message”); } } Then, your code will compile. Note that, in C# 6.0, this will only … Read more
What about cases where you want to reuse the name of a property, for example when throwing exception based on a property name, or handling a PropertyChanged event. There are numerous cases where you would want to have the name of the property. Take this example: switch (e.PropertyName) { case nameof(SomeProperty): { break; } // … Read more
They are syntactic sugar for two different things. The former initializes a backing field, and sets it to the expression on the right hand side of the assignment during field initialization. The latter creates a get that does exactly what is in the expression. public override bool CanRead { get; } = true; is equivalent … Read more
People using TFS 2012 have reported success using: /tv:14.0 /p:GenerateBuildInfoConfigFile=false /p:VisualStudioVersion=14.0 as arguments to MSBuild. Perhaps this might work for you, but so far this does not work for my TFS 2013 build agents. Update: I finally got this to work on TFS 2013. Here is what I had to do: Install VS 2015 or … Read more