I have a more general question: has anyone here built a truly portable app using Mono (i.e. one that runs on several platforms, has a reasonable number of active users and is supported) and can share some insights regarding performance and other issues? If you started today, would you still use Mono?
I can't share the name, but we've built a complete enterprise stack on Mono. There are several parts: - Server, Nancy2/Marten/Hangfire, runs on linux - Headless clients for linux and Windows (x64) - GUI clients for macOS, linux and Windows (x64) The server is deployed as a static fat binary. The headless clients are static binaries for linux and .NET proper for Windows. The GUI clients use Eto, which in turn means: -…
Giving Mono Souper Powers
11–20 of 29 posts
Re: Giving Mono Souper Powers
#12I have a more general question: has anyone here built a truly portable app using Mono (i.e. one that runs on several platforms, has a reasonable number of active users and is supported) and can share some insights regarding performance and other issues? If you started today, would you still use Mono?
I can't share the name, but we've built a complete enterprise stack on Mono. There are several parts: - Server, Nancy2/Marten/Hangfire, runs on linux - Headless clients for linux and Windows (x64) - GUI clients for macOS, linux and Windows (x64) The server is deployed as a static fat binary. The headless clients are static binaries for linux and .NET proper for Windows. The GUI clients use Eto, which in turn means: -…
Also, do your GUI clients have fancier UIs? For example, have you implemented your own grid view, something where you put custom controls in the cells, images, graphics, etc.?
Re: Giving Mono Souper Powers
#13Earlier quoted context omitted.
I can't share the name, but we've built a complete enterprise stack on Mono. There are several parts: - Server, Nancy2/Marten/Hangfire, runs on linux - Headless clients for linux and Windows (x64) - GUI clients for macOS, linux and Windows (x64) The server is deployed as a static fat binary. The headless clients are static binaries for linux and .NET proper for Windows. The GUI clients use Eto, which in turn means: -…
How's Eto? It seems really cool but it's backed by a small company, I think there's just 1 developer. Also, do your GUI clients have fancier UIs? For example, have you implemented your own grid view, something where you put custom controls in the cells, images, graphics, etc.?
Most of the user interaction is happening via the web app served by the server. The local clients are "just" for configuration, comparable in complexity with e.g. Tunnelbear or Glasswire. We use some custom grid elements, which have been easy to implement.
Eto is the only framework out there which gives you native GUIs everywhere. That's what was most important to us. Native speed, native OS integration (tray menus, notifications etc.). It's also really easy to learn for devs who might have been WPF-exclusive before.
Re: Giving Mono Souper Powers
#14Earlier quoted context omitted.
How's Eto? It seems really cool but it's backed by a small company, I think there's just 1 developer. Also, do your GUI clients have fancier UIs? For example, have you implemented your own grid view, something where you put custom controls in the cells, images, graphics, etc.?
We maintain internal forks of Eto and Nancy. They are easy enough to grok for us to modify and maintain, even when development upstream dies. Most of the user interaction is happening via the web app served by the server. The local clients are "just" for configuration, comparable in complexity with e.g. Tunnelbear or Glasswire. We use some custom grid elements, which have been easy to implement. Eto is the only frame…
Thank you for your detailed answer, by the way! :)
Re: Giving Mono Souper Powers
#15I have a more general question: has anyone here built a truly portable app using Mono (i.e. one that runs on several platforms, has a reasonable number of active users and is supported) and can share some insights regarding performance and other issues? If you started today, would you still use Mono?
On Linux the UI is via the browser (the service has a web interface).
I think this is the only C# project I use currently.
Re: Giving Mono Souper Powers
#16Earlier quoted context omitted.
We maintain internal forks of Eto and Nancy. They are easy enough to grok for us to modify and maintain, even when development upstream dies. Most of the user interaction is happening via the web app served by the server. The local clients are "just" for configuration, comparable in complexity with e.g. Tunnelbear or Glasswire. We use some custom grid elements, which have been easy to implement. Eto is the only frame…
A sort of follow-up question: have you contributed things back to Eto? Were they responsive? Thank you for your detailed answer, by the way! :)
Re: Giving Mono Souper Powers
#17I have a more general question: has anyone here built a truly portable app using Mono (i.e. one that runs on several platforms, has a reasonable number of active users and is supported) and can share some insights regarding performance and other issues? If you started today, would you still use Mono?
Re: Giving Mono Souper Powers
#18I have a more general question: has anyone here built a truly portable app using Mono (i.e. one that runs on several platforms, has a reasonable number of active users and is supported) and can share some insights regarding performance and other issues? If you started today, would you still use Mono?
I am the main developer on an open source app called Radarr ( https://github.com/Radarr/Radarr ). It focuses on automatically downloading movies and managing said movies. While we have used mono only one „one“ platform technically (Unix), I would still like to add my own experience, since we encountered some different behaviour on macOS and Linux. Also I have spent the last week or so tracking down memory leaks for o…
What are you going to switch to, btw?
Re: Giving Mono Souper Powers
#19I have a more general question: has anyone here built a truly portable app using Mono (i.e. one that runs on several platforms, has a reasonable number of active users and is supported) and can share some insights regarding performance and other issues? If you started today, would you still use Mono?
Re: Giving Mono Souper Powers
#20I have a more general question: has anyone here built a truly portable app using Mono (i.e. one that runs on several platforms, has a reasonable number of active users and is supported) and can share some insights regarding performance and other issues? If you started today, would you still use Mono?
I left that project two years ago but if starting something similar today I'd probably go with .net core. Not because of any issues with mono, but core just seems like the future. I didn't even realize that mono was still in active development, though I'm not really following that field anymore, so.
Just for the record, I never did notice any memory leaks that others complain about. Our servers stayed running for months at a time with no noticeable leaks.