From 8b5136825c9a14d0669240d5ef331b64798a5080 Mon Sep 17 00:00:00 2001 From: SteveSandersonMS Date: Thu, 7 Jul 2016 14:59:59 +0100 Subject: [PATCH] Update remaining doc references to Invoke and InvokeExport --- src/Microsoft.AspNetCore.NodeServices/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/Microsoft.AspNetCore.NodeServices/README.md b/src/Microsoft.AspNetCore.NodeServices/README.md index 8fdb02a..3fb9928 100644 --- a/src/Microsoft.AspNetCore.NodeServices/README.md +++ b/src/Microsoft.AspNetCore.NodeServices/README.md @@ -184,7 +184,7 @@ var nodeServices = Configuration.CreateNodeServices(new NodeServicesOptions { If you create a `NodeServices` instance this way, you can also dispose it (call `nodeServiceInstance.Dispose();`) and it will shut down the associated Node instance. But because these instances are expensive to create, you should whenever possible retain and reuse your `NodeServices` object. They are thread-safe - you can call `nodeServiceInstance.InvokeAsync(...)` simultaneously from multiple threads. -### Invoke<T> +### InvokeAsync<T> **Signature:** @@ -264,7 +264,7 @@ There's a working image resizing example following this approach [here](https:// * A JSON-serializable .NET type, if your JavaScript code uses the `callback(error, result)` pattern to return an object, as in example 1 above * Or, the type `System.IO.Stream`, if your JavaScript code writes data to the `result.stream` object (which is a [Node `Duplex` stream](https://nodejs.org/api/stream.html#stream_class_stream_duplex)), as in example 2 above -### InvokeExport<T> +### InvokeExportAsync<T> **Signature**