Skip to content

Commit 97d1971

Browse files
authored
Merge pull request #200341 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 8dfa857 + a0c9f01 commit 97d1971

File tree

5 files changed

+6
-6
lines changed

5 files changed

+6
-6
lines changed

articles/azure-functions/create-first-function-vs-code-other.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -167,7 +167,7 @@ The *function.json* file in the *HttpExample* folder declares an HTTP trigger fu
167167
Err(_) => 3000,
168168
};
169169
170-
warp::serve(example1).run((Ipv4Addr::UNSPECIFIED, port)).await
170+
warp::serve(example1).run((Ipv4Addr::LOCALHOST, port)).await
171171
}
172172
```
173173

articles/azure-functions/durable/durable-functions-dotnet-entities.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -267,7 +267,7 @@ We also enforce some additional rules:
267267
* Entity interface methods must not have more than one parameter.
268268
* Entity interface methods must return `void`, `Task`, or `Task<T>`.
269269

270-
If any of these rules are violated, an `InvalidOperationException` is thrown at runtime when the interface is used as a type argument to `SignalEntity` or `CreateProxy`. The exception message explains which rule was broken.
270+
If any of these rules are violated, an `InvalidOperationException` is thrown at runtime when the interface is used as a type argument to `SignalEntity`, `SignalEntityAsync`, or `CreateEntityProxy`. The exception message explains which rule was broken.
271271

272272
> [!NOTE]
273273
> Interface methods returning `void` can only be signaled (one-way), not called (two-way). Interface methods returning `Task` or `Task<T>` can be either called or signalled. If called, they return the result of the operation, or re-throw exceptions thrown by the operation. However, when signalled, they do not return the actual result or exception from the operation, but just the default value.

articles/azure-functions/durable/durable-functions-phone-verification.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ The **E4_SendSmsChallenge** function uses the Twilio binding to send the SMS mes
9595
[!code-csharp[Main](~/samples-durable-functions/samples/precompiled/PhoneVerification.cs?range=72-89)]
9696

9797
> [!NOTE]
98-
> You will need to install the `Microsoft.Azure.WebJobs.Extensions.Twilio` Nuget package to run the sample code.
98+
> You must first install the `Microsoft.Azure.WebJobs.Extensions.Twilio` Nuget package for Functions to run the sample code. Don't also install the main [Twilio nuget package](https://www.nuget.org/packages/Twilio/) because this can cause versioning problems that result in build errors.
9999
100100
# [JavaScript](#tab/javascript)
101101

articles/azure-functions/functions-bindings-storage-queue-trigger.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -363,7 +363,7 @@ See the [Example section](#example) for complete examples.
363363
364364
::: zone pivot="programming-language-csharp"
365365

366-
The usage of the Blob trigger depends on the extension package version, and the C# modality used in your function app, which can be one of the following:
366+
The usage of the Queue trigger depends on the extension package version, and the C# modality used in your function app, which can be one of the following:
367367

368368
# [In-process class library](#tab/in-process)
369369

@@ -528,4 +528,4 @@ The host.json file contains settings that control queue trigger behavior. See th
528528
<!-- LINKS -->
529529

530530
[CloudQueueMessage]: /dotnet/api/microsoft.azure.storage.queue.cloudqueuemessage
531-
[QueueMessage]: /dotnet/api/azure.storage.queues.models.queuemessage
531+
[QueueMessage]: /dotnet/api/azure.storage.queues.models.queuemessage

articles/notification-hubs/notification-hubs-windows-store-dotnet-get-started-wns-push-notification.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ To send push notifications to UWP apps, associate your app to the Windows Store.
9191
### Configure WNS settings for the hub
9292

9393
1. In the **NOTIFICATION SETTINGS** category, select **Windows (WNS)**.
94-
2. Enter values for **Package SID** and **Security Key** (the **Application Secret**) you noted from the previous section.
94+
2. Enter values for **Package SID** (like this "ms-app://`<Your Package SID>`") and **Security Key** (the **Application Secret**) you noted from the previous section.
9595
3. Click **Save** on the toolbar.
9696

9797
![The Package SID and Security Key boxes](./media/notification-hubs-windows-store-dotnet-get-started/notification-hub-configure-wns.png)

0 commit comments

Comments
 (0)