c#-5.0

Both the System. Reactive extension for .NET and new C# 5.0 (.NET 4.5) async/await pursue (or based on) future and promises constructs paradigm (approach). Can you give the (*) simplest C# code example illustrating the difference between them? (*) Is it possible without I/O, internet or database connections? Update: Well, let me reformulate if this question seemed to be answered before. Why would one add and start using Reactive (Rx) extensions for .NET while using native .NET Iobservable / IObserver + await/async ? What are the possible illustrations of what one will be missing from Rx that

I have a method in ASP.NET application, that consumes quite a lot of time to complete. A call to this method might occur up to 3 times during one user request, depending on the cache state and parameters that user provides. Each call takes about 1-2 seconds to complete. The method itself is synchronous call to the service and there is no possibility to override the implementation. So the synchronous call to the service looks something like the following: public OutputModel Calculate(InputModel input) { // do some stuff return Service.LongRunningCall(input); } And the usage of the method is

lets say i have class called x and y like this class x { public x() { p(); } private async p() { await q(); } private async p() { //some logic is there } } in test.aspx.cs file i am trying to create an instance of this class x object =new x(); when i run this i get an exception at runtime saying : An asynchronous operation cannot be started at this time. Asynchronous operations may only be started within an asynchronous handler or module or during certain events in the Page lifecycle. If this exception occurred while executing a Page, ensure that the Page is marked <%@ Page Async="true" %>.

I just start learn ReactiveUI from https://github.com/reactiveui/ReactiveUI.Samples/blob/master/ReactiveUI_4Only.Samples.sln . I download lastest version via nuget but I cant find class ReactiveAsyncCommand in ReactiveUI.Xaml. ReactiveAsyncCommand is now in ReactiveUI.Legacy . 来源： https://stackoverflow.com/questions/17792826/reactiveasynccommand-missing-in-reactiveui-5-0-2

I built some async/await demo console app and get strange result. Code: class Program { public static void BeginLongIO(Action act) { Console.WriteLine("In BeginLongIO start... {0} {1}", (DateTime.Now.Ticks - ticks) / TimeSpan.TicksPerMillisecond, Thread.CurrentThread.ManagedThreadId); Thread.Sleep(1000); act(); Console.WriteLine("In BeginLongIO end... \t{0} {1}", (DateTime.Now.Ticks - ticks) / TimeSpan.TicksPerMillisecond, Thread.CurrentThread.ManagedThreadId); } public static Int32 EndLongIO() { Console.WriteLine("In EndLongIO start... \t{0} {1}", (DateTime.Now.Ticks - ticks) / TimeSpan

When I analyse code coverage in Visual Studio 2012, any of the await lines in async methods are showing as not covered even though they are obviously executing since my tests are passing. The code coverage report says that the uncovered method is MoveNext , which is not present in my code (perhaps it's compiler-generated). Is there a way to fix code coverage reporting for async methods? Note : I just ran coverage using NCover, and the coverage numbers make a lot more sense using that tool. As a workaround for now, I'll be switching to that. This can happen most commonly if the operation you're