Show Application's Tray Icon for all user logon - wpf

I have written a WPF windows tray app.
A Mutex is using to prevent multiple instances of the same program from running. The app has been installed on a windows server.
Problem:
Windows tray Icon is visible only to the user who has run it. When another user login to server, the windows tray icon is gone.
What should I do for the windows tray to be visible to all users in different login sessions?

Related

Redirect user to permission settings in ReactJS

I'm building a ReactJS app that requires location, camera and flashlight permissions. The problem is that most (if not all) browsers only ask for permissions once. Once denied, it will never ask again.
In the Chrome browser on my PC I can manually enable permissions by clicking the corresponding icon in the URL bar:
However, in Android and iOS the app is supposed to run inside a mini webview without the URL. So I will need to redirect the user to the corresponding settings in the browser manually.
I've browsed through quite some solutions on SO but they all refer to the navigator permissions method which can only ask for permissions once.
How do I direct the user to the specific site settings in Android and iOS?

Detect browser close and logout user in .Net Core 5

I am working on an application in Asp.Net Core 5. In this application, we need to manage users.
If a user does login in the application and closes the browser, he/she will be automatically logged out from the application.
How can I catch the browser close event and logout the user.
NB: User logout time should be written in database.

Recaptcha is not valid in Microsoft Teams tab app

I have a tab app which uses a popup window (microsoftTeams.tasks.startTask) to login the user. This popup window contains an iframe to my actual website login. This login flow completely works in the web version of Microsoft Teams (it saves the cookie and logs in the user), but it doesn't in the desktop app. The iframe in the Teams popup window gives me this error: {"error":"recaptcha_not_valid"}.
What can be the problem?

How to grant audio/camera permissions in Electron after it was rejected?

I'm building a desktop app with Electron and React. When it first starts up checks if the user has allowed access to Camera, Screen, and Audio permissions. On windows, this is granted automatically, and on MacOS there is a popup that asks users to allow perms.
In the event a user clicks deny permissions, this modal will popup. I want to be able to hit the 'Grant permissions' button, and all denied permissions will get updated to allowed.
If this is not possible, is there an easy way to navigate to the device settings app to get users to change their settings? I have reviewed https://www.electronjs.org/docs/latest/api/window-open but this seems geared towards websites, rather than native applications.

Login using Azure from a Capacitor built app opens a new login window outside the app

I am using capacitor 3.0 to build a native iOS app with React.
The app's user is expected to login first.
I want the user's login to be handled by Microsoft Azure ActiveDirectory B2C and followed this tutorial to set this up:
https://learn.microsoft.com/en-us/azure/active-directory/develop/tutorial-v2-react
Furthermore, Microsoft offers a Microsoft Authentication Library (MSAL, https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-browser/docs/login-user.md), which for a login redirects to a screen managed by microsoftonline.com to take the username and password. This is a standard login interface by Microsoft, which can be custom-branded but I have not made that change. Just using the standard MS UI.
This redirect works fine in a Web/desktop browser as it opens the Microsoft login screen within the same page without opening a new browser window.
However, when accessing the login from within the Capacitor built iOS app, the user is taken to an external browser for the login, which breaks the user experience.
Any ideas on why capacitor launches a browser for login when this is not the case with the regular React web browser (non-Capacitor)?

Resources