Local Notifications Demo for Windows

[true-perfect-code]

Is there a specific reason why you can't find an example of local notification in Windows anywhere?

This is also the case here in your example, you can see the implementation for Android and iOS but not for Windows?

Thanks to the gitHub project by @gurrenm3 (see https://github.com/gurrenm3/Toast-Notifications-with-.Net-Maui), I am able to generate a local notification with MAUI for Windows a desktop app , but there is a big problem here. It is not possible to read the passed ID of the notification when restarting the Windows app. This is particularly frustrating if you are managing f.e. calender events, and the app opens (after the user has clicked on the notification displayed in Windows), because then the user has to select the corresponding calendar entry himself!

So can someone here please explain how to properly implement a local notification in a MAUI Windows desktop with passed ID? Or is this not possible at all?

The corresponding project is here https://github.com/true-perfect-code/MAUIWinDesktopLocalNotif/tree/master

Thanks a lot
pc

[jfversluis]

I'm not 100% sure why Windows was not included for this sample.

However, as for the rest of this issue, I don't think this is the right place to ask these questions. This will probably be better on the .NET MAUI repo in the Discussions tab, Microsoft Q&A or a third-party forum like Stack Overflow. Or maybe ask your favorite Copilot!

And since this is even specific to Windows it might even be worth it to find WinUI specific resources to see how its done. These will probably yield more and better answers than what you will get here :)

Good luck!

[true-perfect-code]

Dear @jfversluis
Am I seeing this correctly and is this Github dotnet/maui-samples (with the accent on maui-samples)?
If so, then I don't necessarily see the point of reporting to other repos.

Please don't be angry with me, but for each of my MAUI problems you refer the responsibility to another place and close my post. This gives me the impression that you only want to reduce the number of open issues at MAUI.

I understand that, of course, and it is frustrating that MAUI has so many open issues, but I don't think that anyone who wants to use MAUI productively is interested in how many open issues MAUI currently has, but that we are all interested in finding a solution. If you refer the problem to other places and then to other places, it's very frustrating and you don't get any results.

I want to take this opportunity, since you are on the Microsoft team, to say something else about MAUI in the hope that microsoft will think about it:
I switched to Flutter once in the last two years because there was a problem with WebView (I'm sure you remember) and MAUI Blazor wasn't working as a result. As far as I can remember, the problem was reported in August and in November I had to switch a small customer project to Flutter. When after many months the problem with WebView was solved, I went back to MAUI Blazor.Now 2 years after MAUI release I had to change my contract with the customer because a publish of MAUI Blazor + RCL + Blazor Web still does not work in Visual Studio although this problem exists since the beginning (so for sure over 2 years).
Most recently I reported this problem to Visual Studio Team (see https://developercommunity.visualstudio.com/t/MAUI-NET-9-:-Publish-windows-desktop-not/10817425?ref=native&refTime=1734779656752&refUserId=7204443e-3c16-6f6e-b445-8beeaa37a645) because it still does not work in NET 9!

And before you say here that this problem has absolutely nothing to do with MAUI (which is correct) I want to ask you to think about the context of such problems. Whether we developers can't use MAUI because there are MAUI bugs or because Visual Studio doesn't compile or link correctly, we don't really care, because in the end we can't deliver what our customers have paid for.That's why I really don't understand why MAUI Team doesn't seem to care if everything around MAUI (Visual Studio, Blazor etc.) works)!I would have expected here e.g. with the MAUI Blazor + RCL + Blazor Web problem that both teams would join forces and some pressure would come from MAUI Team to VS Team so that this problem would be solved in a few weeks.But what do we have in reality?More than 2 years of the same problem and I wonder if anyone has ever managed a publish with Visual Studio + MAUI Blazor + RCL + Blazor Web?

By the way, I ask ChatGPT at least 1-2 times a month if there is an alternative to MAUI, but there is not and I have to live with MAUI problems, but every day I ask myself if the energy I invest here is still useful at all. at the moment MAUI is a hobby for me because I don't dare to deliver anything to the customers in MAUI and limit myself to Blazor.But I think that many developers feel the same way (when I read posts on the internet).

Once again: it really doesn't matter how many open issues MAUI has, the only thing that matters to us developers is whether MAUI Team deals with them or not. If you close my post in this way, then I know that nobody will deal with it. But if you try to find a solution here, then I don't care if MAUI still has 10,000 open issues , because then I have hope that my open issues will also be addressed one day.

Please think about what I have written, don't take it badly and be aware that we are aware that MAUI team is very small and there are many other problems that have led to this state. But for this problem (very small MAUI team)), however, the correct contact address is your employer microsoft.

Regards
pc

[jfversluis]

Thanks for raising this and I'm sorry you feel this way. But I think there is some misunderstanding here.

This is indeed the .NET MAUI samples repository, which is basically a repository that exists because we, the .NET MAUI team, want to do something extra, showing you how certain things are done. There is no dedicated time on the clock for us to work on this, that also means there is also no support on these samples. These samples are provided as-is and if they are helpful that's great, if they're not that is too bad and means that you will have to do some digging yourself. That said, we will help out where we can if we have time available.

Your first question is valid: why is there no Windows sample included? But then the rest of your issue basically describes how it could be done (that's great! Maybe consider opening a PR for this samples repo to also include Windows) and then asks how to solve a specific problem. And don't get me wrong, I appreciate the information and we're always happy to help, but this is not the right place for that.

The issues here are for whenever something is wrong with a sample or you want to request something new. Again, a good example is: please include Windows in the local notifications. But this is not a support channel for .NET MAUI as a product.

Additionally, the way I understand what you're writing, I don't even think this is a bug in .NET MAUI itself, so that also makes it unsuitable to open an issue on the .NET MAUI product repo. This is more of a "how do I do x with MAUI" question which is perfect to be asked in the channels I pointed you to.

I understand that from a customer perspective all the different places to report something isn't ideal and we're trying our best to help you out even if something isn't necessarily our area, but we're a big company with many different products and while it might all seem like the same thing to you, I can assure you it definitely is not. My main concern is unblocking you and helping you further, not bringing any number of issues down. But if I keep answering questions on this repository, more people will start to think this is the right place to do that, and now we have yet another place to maintain which is no something that we can do unfortunately.

Hopefully this will make it a little more clear. If you have any other concerns about the product, feel free to reach out, my email is on my GitHub profile, maybe I can take some of your doubts away.

Thanks!

[true-perfect-code]

Dear @jfversluis

I apologize if my post sounded too personal. My intention was actually to give the MAUI team an impulse to discuss these problems internally with “higher” authorities => But for this problem (very small MAUI team)), however, the correct contact address is your employer microsoft.

Even before my student days I programmed in DOS/Windows with C, later C++ MFC and then came the NET time. So I am well aware of how complex the Microsoft world is.

However, I think that Microsoft (here I am not thinking of MAUI Team) should finally decide for itself whether (and in which) tools for development should still be invested. We all agree that Microsoft is doing well and should stay that way, but it is a paradox that Microsoft makes the most profit with: Azure, Office and OS yet there is no sign of either MAUI or Blazor being introduced in these areas but they continue to rely on Java, Python, Go, C++.

If microsoft wants to run MAUI and blazor as a hobby and that's why your teams are so small, then that should be clearly communicated to us developers.
But if microsoft is serious, then they should first fully integrate MAUI / Blazor into their own products and then microsoft will definitely come to the conclusion that the number of MAUI developers should be significantly increased.

@jfversluis please don't get me wrong here, as all developers (MAUI team included) are on the same side. But the situation we are in has nothing to do with programming but with strategic decisions that none of us know (I mean, only Microsoft C-Suite knows). MAUI team then complains about missing employees and we developers are annoyed about MAUI bugs. The worst thing that can happen is that we developers make mistakes against you (the MAUI team) because that would be unfair. But my frustration is directed mainly at the Microsoft C-Suite who make the strategic decisions that ultimately put us in this situation.

Now I don't think we should continue with this topic. Please check internally whether the voice from outside (voices of programmers who still use MAUI) can be heard internally at higher levels at microsoft, then it will resolve itself.

Thank you
pc