Skip to content

Commit 6db24c7

Browse files
committed
Correct numbering
1 parent b69c4e0 commit 6db24c7

1 file changed

Lines changed: 6 additions & 9 deletions

File tree

hub/apps/develop/notifications/push-notifications/push-quickstart.md

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -114,10 +114,10 @@ using namespace winrt::Microsoft::Windows::PushNotifications;
114114
115115
If you get a "Can't find Microsoft.Windows.PushNotifications" error, that likely means the header files haven't been generated. Build the app without the namespaces first (keep the includes without an error), then try adding them in again.
116116
117-
### Step 2: Add your COM activator to your app's manifest
117+
### Step 3: Add your COM activator to your app's manifest
118118
119119
> [!IMPORTANT]
120-
> If your app is unpackaged (that is, it lacks package identity at runtime), then skip to **Step 3: Register for and respond to push notifications on app startup**.
120+
> If your app is unpackaged (that is, it lacks package identity at runtime), then skip to **Step 4: Register for and respond to push notifications on app startup**.
121121
122122
If your app is packaged (including packaged with external location):
123123
Open your **Package.appxmanifest**. Add the following inside the `<Application>` element. Replace the `Id`, `Executable`, and `DisplayName` values with those specific to your app.
@@ -152,9 +152,9 @@ Open your **Package.appxmanifest**. Add the following inside the `<Application>`
152152
```
153153

154154
>[!NOTE]
155-
> An example of the completed C++ class for the sample can be found [after Step 4](#sample-code). Steps 3 and 4 provide step-by-step guidance to add each piece in the final sample.
155+
> An example of the completed C++ class for this example can be found [after Step 5](#example-code). Steps 4 and 5 provide step-by-step guidance to add each piece in the final example.
156156

157-
### Step 3: Register for and respond to push notifications on app startup
157+
### Step 4: Register for and respond to push notifications on app startup
158158

159159
Update your app's `main()` method to add the following:
160160

@@ -180,7 +180,7 @@ Next, add a check if the PushNotification APIs are supported with [PushNotificat
180180
181181
Now that there's confirmed push notification support, add in behavior based on [PushNotificationReceivedEventArgs](/windows/windows-app-sdk/api/winrt/microsoft.windows.pushnotifications.pushnotificationreceivedeventargs).
182182
183-
### Step 4: Request a WNS Channel URI and register it with the WNS server
183+
### Step 5: Request a WNS Channel URI and register it with the WNS server
184184
185185
WNS Channel URIs are the HTTP endpoints for sending push notifications. Each client must request a Channel URI and register it with the WNS server to receive push notifications.
186186
@@ -200,10 +200,7 @@ winrt::guid remoteId{ "00000000-0000-0000-0000-000000000000" }; // Replace this
200200
201201
The **PushNotificationManager** will attempt to create a Channel URI, retrying automatically for no more than 15 minutes. Create an event handler to wait for the call to complete. Once the call is complete, if it was successful, register the URI with the WNS server.
202202
203-
> [!NOTE]
204-
> To use LOG_HR_MSG included in the following code chunks, use Package Manager to import `Microsoft.Windows.ImplementationLibrary`, version 1.0.220914.1.
205-
206-
## Sample Code
203+
## Example Code
207204
208205
```cpp
209206
#include <iostream>

0 commit comments

Comments
 (0)