We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It looks like socket-based implementation is best in terms of portability.
https://stackoverflow.com/questions/5366316/simple-cross-platform-process-to-process-communication-in-mono
https://docs.microsoft.com/ru-ru/dotnet/api/system.net.sockets.socket?view=netframework-4.7.2
The text was updated successfully, but these errors were encountered:
Port single instance implementation
d0b534b
Introduce --no-tray-icon cmdline option
acf1690
GH-16
Replace --no-tray-icon with --tray-icon (tray icon support disabled b…
dbd41fb
…y default) GH-16
No branches or pull requests
It looks like socket-based implementation is best in terms of portability.
https://stackoverflow.com/questions/5366316/simple-cross-platform-process-to-process-communication-in-mono
https://docs.microsoft.com/ru-ru/dotnet/api/system.net.sockets.socket?view=netframework-4.7.2
The text was updated successfully, but these errors were encountered: