c#-5.0

I'm learning about async/await, and ran into a situation where I need to call an async method that should return an object or list of same object. Is this the right way to implement ? from AManager.cs public async Task Initialize(string objectPath) { AnObject someObject = await BClass.GetAnObject(objectPath); } and this is the called method Class B: public async Task<AnObject> GetAnObject(string objectPath) { AnObject someObj = new AnObject(); return someObj; } What happens if I want to return a list of object ? I should create a wrapper that contains a list ? and return that wrapper ? Because

Microsoft has updated the async/await targeting for .net 4.0 and now suggests using the Microsoft.Bcl.Async library available on nuget . In the release notes, it states that .net 4 with KB 2468871 is required. Is KB2468871 a build requirement or a deployment requirement? What aspect of KB2468871 makes it required? Quoting from http://support.microsoft.com/kb/2468871/en-us Feature 5 Changes to the support portable libraries. These changes include API updates and binder modifications. This update enables the CLR to bind successfully to portable libraries so that a single DLL can run on the .NET

I've started to build a tcp server which will be able to accept many clients, and receive simultaneously from all of the clients new data. Until now, I used IOCP for tcp servers which was pretty easy and comfortable, but this time I want to use the Async / Await tech. that was released in C# 5.0. The problem is that when I started to write the server using async / await, I figured out that in tcp multiple users server use case, async / await tech. and the regular synchrony methods will work the same. Here's a simple example to be more specific: class Server { private TcpListener _tcpListener;

Task or Task<TResult> object is awaitable, so we can use await key on those whose return value is Task or Task<TResult>. Task or Task<TResult> are the most frequently-used awaitable object. We also can define our own awaitable object.The object should has below qualification. It has a GetAwaiter() method (instance method or extension method); Its GetAwaiter() method returns an awaiter. An object is an awaiter if: It implements INotifyCompletion or ICriticalNotifyCompletion interface; It has an IsCompleted, which has a getter and returns a Boolean; it has a GetResult() method, which returns

Recently Jon Skeet at NDC London spoke about C# 5 async/await and presented the idea of " ordering by completion " a list of async tasks. A link http://msmvps.com/blogs/jon_skeet/archive/2012/01/16/eduasync-part-19-ordering-by-completion-ahead-of-time.aspx I am a bit confused or should I say I am not sure when will this technique be more appropriate to use. I cannot understand the difference between this and the below example var bag = new ConcurrentBag<object>(); Parallel.ForEach(myCollection, async item => { // some pre stuff var response = await GetData(item); bag.Add(response); // some