Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix C# code compile erros #3940

Open
wants to merge 2 commits into
base: docs
Choose a base branch
from

Conversation

KubaSzostak
Copy link

This fix doesn't make this sample working. It just makes the C# code be able to be compiled.


Other issues

  • There is no C# code in Step 5.
  • There is no C# code in Step 6.
  • In Step 3 there is reference to ToastWithTextBox.ScenarioId which is not implemented anywhere.
  • Calling AppNotificationManager.Default.Register(); throws Error HRESULT E_FAIL has been returned from a call to a COM component error.

For me Getting started example could loook something like:

public static bool SendNotificationToast(string title, string message)
{
    var xmlPayload = new string($@"
        <toast>    
            <visual>    
                <binding template=""ToastGeneric"">    
                    <text>{title}</text>
                    <text>{message}</text>    
                </binding>
            </visual>  
        </toast>");

    var toast = new AppNotification(xmlPayload);
    AppNotificationManager.Default.Show(toast);
    return toast.Id != 0;
}

It's good starting point for the developer wanting to notify the user about something (not always it's important what the user will do with the notification). In such case there is no need for updating the Package.appxmanifest file, nor to build NotificationManager. Single function with few lines of code is enough for that :-)

This fix doesn't make this sample working. It just makes the C# code be able to be compiled.

---

**Other issues**

- There is no C# code in [Step 5](https://docs.microsoft.com/en-us/windows/apps/windows-app-sdk/notifications/app-notifications/app-notifications-quickstart?tabs=cs#step-5-process-a-user-selecting-a-notification).
- There is no C# code in [Step 6](https://docs.microsoft.com/en-us/windows/apps/windows-app-sdk/notifications/app-notifications/app-notifications-quickstart?tabs=cs#step-6-remove-notifications).
- In *Step 3* there is reference to `ToastWithTextBox.ScenarioId` which is not implemented anywhere.
- Calling `AppNotificationManager.Default.Register();` throws *Error HRESULT E_FAIL has been returned from a call to a COM component* error.

---

For me *Getting started* example could loook something like:

```cs
public static bool SendNotificationToast(string title, string message)
{
    var xmlPayload = new string($@"
        <toast>    
            <visual>    
                <binding template=""ToastGeneric"">    
                    <text>{title}</text>
                    <text>{message}</text>    
                </binding>
            </visual>  
        </toast>");

    var toast = new AppNotification(xmlPayload);
    AppNotificationManager.Default.Show(toast);
    return toast.Id != 0;
}

It's good starting point for the developer wanting to notify the user about something, where it's not important what the user will do with the notification. In such case there is no need for updating the `Package.appxmanifest` file, nor to build `NotificationManager`. Single function with few lines of code is enough for that :-) 
```
@ghost
Copy link

ghost commented Jul 13, 2022

CLA assistant check
All CLA requirements met.

@PRMerger14
Copy link
Contributor

@KubaSzostak : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Jak-MS
Copy link
Contributor

Jak-MS commented Jul 13, 2022

@vaheeshta

Can you review this PR?

IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@PRMerger4 PRMerger4 added the aq-pr-triaged tracking label for the PR review team label Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants