[HELP]Using Uwp.Notifications in VSTO(winforms)

[beatofangel]

I have a VSTO Add-in project using Uwp.Notifications to toast local notifications. It works fine when I debug it locally.
But it seems that Uwp.Notifications doesn't work in some cases and throws an exception.

System.ArgumentException: The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
at Microsoft.Toolkit.Uwp.Notifications.ToastContentBuilder.Show(CustomizeToast customize)
...

I have tried several scenarios and the results are listed below.

Debug Mode (Visual Studio)	Install from local vsto manifest	Clickonce (Install via UNC)	Clickonce (Install via http/https)
✔	✔	✔	❌

After googling for a long time, I still haven't got any clue to solve this problem.
Does Uwp.Notifications have any restrictions on Apps or Add-ins published via clickonce and installed from internet via http/https?

[ghost]

Hello beatofangel, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[ghost]

This issue has been marked as "needs attention 👋" due to no activity for 15 days. Please triage the issue so the fix can be established.

[ghost]

Hello beatofangel, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[michael-hawker]

FYI @andrewleader

[andrewleader]

Hmm... I haven't tested all add-in scenarios related to ClickOnce. What I would recommend is trying the new WinAppSDK AppNotifications API: https://docs.microsoft.com/en-us/windows/apps/windows-app-sdk/notifications/app-notifications/app-notifications-quickstart?tabs=cs

We're moving the Toolkit Notifications library to WinAppSDK and that'll be where all investments will be made going forward (and in version 1.2 of WinAppSDK, they're adding Builder APIs similar to the Builder APIs in the Toolkit today). If the WinAppSDK API works, then that's promising news and you should use that. If the WinAppSDK API has the same issue, then you can file an issue on the WinAppSDK GitHub repo, and the dev team will be able to look at it: https://github.com/microsoft/WindowsAppSDK/issues

[michael-hawker]

FYI @vaheeshta