MonoDevelop VS bubblewrap

An older version of the underlying source code remains available: https://github.com/mono/monodevelop

From what I understand MonoDevelop has been discontinued. Even their repo has been archived.

SharpDevelop and MonoDevelop are both dead and focused for devs which gives them different priority than apps targeted at non-devs, but they show how to put together seriously complex apps, and they're the ancestor of the Visual Studio for Mac.

Monodevelop

There are Linux binaries for MonoDevelop which is what VS for Mac is based on.

Using Visual Studio with Wine is not really possible. But you have other IDEs as options. You can pack Visual Studio Code with the needed plugins. You can use MonoDevelop which is the IDE from the Mono project https://www.monodevelop.com/. Something to add here, the Mono project is actually developed by Microsoft. And there is Jetbrains Rider, I personally use it every day at work and am kind of in love, but it costs you 139 € in the first year.

Nothing nix specific but you may be interested in https://github.com/containers/bubblewrap

Recently, I came across Chainguard and wrote the article How to build Docker Images with Melange and Apko. As a fervent supporter of Kubernetes and GitLab CI, I was eager to experiment with building images using Melange in this particular setup. GitLab's shared Runners work seamlessly with Bubblewrap, eliminating the need for additional configurations. This post is intended for enthusiasts like myself, interested in hosting their own Kubernetes Runners and leveraging the Kubernetes Runner Type of Melange.

```

This is basically manually invoking what Flatpak does:

https://github.com/containers/bubblewrap

This is also useful for more than just security. E.G., you can test how your app would behave on a fresh install by masking your user configuration files. I personally also have a tool that uses it to basically bundle all dependencies from an entire Linux distribution in order to make highly portable AppImages— Been meaning to post that, will get around to it eventually maybe.

The flags above should hide your user data (`--tmpfs`), disable network access (`--unshare-all`), hide/virtualize devices and OS state (`--dev` and `--proc`), and make the rest of the root filesystem read-only (`--ro-bind`­— Including the insecure X11 socket in `/tmp`, which you might want to expose for GUI apps).

Check them against `bwrap --help`; I might have omitted one or two more things you'd need.

While trying to find out more comparison information, found this light on details issue:

https://github.com/containers/bubblewrap/issues/81

It mentions nsjail and minijail.