This is an expression-bodied property, a new syntax for computed properties introduced in C# 6, which lets you create computed properties in the same way as you would create a lambda expression. This syntax is equivalent to public bool property { get { return method(); } } Similar syntax works for methods, too: public int … Read more
I like James’ suggestion of using an extension method. There is just one problem: although you’re using nameof() and have eliminated magic strings, there’s still a small issue of type safety: you’re still working with strings. As such, it is very easy to forget to use the extension method, or to provide an arbitrary string … Read more
While you could initialize a dictionary with collection initializers, it’s quite cumbersome. Especially for something that’s supposed to be syntactic sugar. Dictionary initializers are much cleaner: var myDict = new Dictionary<int, string> { [1] = “Pankaj”, [2] = “Pankaj”, [3] = “Pankaj” }; More importantly these initializers aren’t just for dictionaries, they can be used … 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
You can’t use nameof to achieve that, but how about this workaround: The below uses no direct reflection (just like nameof) and no explicit method name. Results.Add(GetCaller(), result); public static string GetCaller([CallerMemberName] string caller = null) { return caller; } GetCaller returns the name of any method that calls it.
Just a guess @(Model?.Person?.Zip)
Using string interpolation in C# is compiled into a simple call to String.Format. You can see with TryRolsyn that this: public void M() { string name = “bar”; string result = $”{name}”; } Is compiled into this: public void M() { string arg = “bar”; string text = string.Format(“{0}”, arg); } It’s clear that this … Read more
In C# 6, get; only properties are only settable from the constructor. From everywhere else, it is read-only. A property with a private set; can be set from everywhere inside that class.
In addition to the several fine answers you already have here: there is a very important difference between an exception filter and an “if” in a catch block: filters run before inner finally blocks. Consider the following: void M1() { try { N(); } catch (MyException) { if (F()) C(); } } void M2() { … 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