c#-5.0

async void unit tests cannot be run within Visual Studio 2012: [TestClass] public class MyTestClass { [TestMethod] public async void InvisibleMyTestMethod() { await Task.Delay(1000); Assert.IsTrue(true); } } If I want to have an asynchronous unit test, the test method has to return a Task: [TestMethod] public async Task VisibleMyTestMethod() { await Task.Delay(1000); Assert.IsTrue(true); } Why is it so? Not that I absolutely need to have an async void test method, I am just curious. Visual Studio 2012 gives no warning nor error when you build an async void test method even though it won't be

A little background information. I am learning the Web API stack and I am trying to encapsulate all data in the form of a "Result" object with parameters such as Success and ErrorCodes. Different methods however, would produce different results and error codes but the result object would generally be instantiated the same way. To save some time and also to learn more about async/await capabilities in C#, I am trying to wrap all the method bodies of my web api actions in an asynchronous action delegate but got caught in a bit of a snag... Given the following classes: public class Result {

Background We have a project that we're developing in VS 2015 with C#6 enabled that occasionally needs to be opened by developers using VS 2013 without C#6. We have no intention to use C# 6 within this particular solution (as much as I'd like to). Problem Visual Studio and ReSharper suggest helpful C# 6 language constructs that render the solution inoperable in earlier versions of Visual Studio without C#6 support. I've disabled the ReSharper C#6 support but I can't seem to disable / limit C# features across the whole solution. Question How do I limit C# to C#5 capabilities within a solution

I need to call an async method in a catch block before throwing again the exception (with its stack trace) like this : try { // Do something } catch { // <- Clean things here with async methods throw; } But unfortunately you can't use await in a catch or finally block. I learned it's because the compiler doesn't have any way to go back in a catch block to execute what is after your await instruction or something like that... I tried to use Task.Wait() to replace await and I got a deadlock. I searched on the Web how I could avoid this and found this site . Since I can't change the async methods

In .NET 4.5 / C# 5, IReadOnlyCollection<T> is declared with a Count property: public interface IReadOnlyCollection<out T> : IEnumerable<T>, IEnumerable { int Count { get; } } I am wondering, wouldn't it have made sense for ICollection<T> to implement the IReadOnlyCollection<T> interface as well: public interface ICollection<T> : IEnumerable<T>, IEnumerable, *IReadOnlyCollection<T>* This would've meant that classes implementing ICollection<T> would've automatically implemented IReadOnlyCollection<T> . This sounds reasonable to me. The ICollection<T> abstraction can be viewed as an extension of

I have an async method: public async Task<bool> ValidateRequestAsync(string userName, string password) { using (HttpClient client = new HttpClient()) { HttpResponseMessage response = await client.GetAsync(url); string stringResponse = await response.Content.ReadAsStringAsync(); return bool.Parse(stringResponse); } } I call this method like this: bool isValid = await ValidateRequestAsync("user1", "pass1"); Can i call the same method from an synchronous method, without using await keyword? Ex: public bool ValidateRequest(string userName, string password) { return ValidateRequestAsync(userName,