AppImageLauncher VS winapps

Every file that you want to execute has to be in your environment PATH. I would also advise to put symlinks and personal executables in ~/.local/bin and put that to your path. Since your user has ownership over that directory, you won't have any probs with permissions that may or may not occur at all. Since we're talking about AppImage files, you might also want to take a look at AppImageLauncher which does a pretty good job at creating entries for your Desktop Menu for the AppImage files that you install to your system.

I think it's safe to install it directly as it stores everything in a single directory. For AppImages there is also AppImagePool + AppImageLauncher (can be installed rootless, useful for better integration of appimages).

This reminds me of a prettier version of AppImageLauncher. Is there also an "Uninstall" option in the right-click menu of the app launcher?

I'm using AppImageLauncher on Fedora.

"... I recall that this was related to an issue with most Electron apps, wherein the AppImage cannot be integrated with the desktop or the favourites bar. So far we've found that the AppImageLauncher (https://github.com/TheAssassin/AppImageLauncher) helps with getting around this!

This one might be controversial, but Winapps for Linux, app that lets run apps from within a Windows KVM as if it were native on your Linux system (https://github.com/Fmstrat/winapps)

Yes but you have to run visual studios in a windows virtual machine qemu/kvm/virtmanager Then pass virtual studio window to your desktop so it runs like it is native https://github.com/Fmstrat/winapps optional Then use winapps to make a desktop and application launcher menu entry/icon

There's something called winapps which works over RDP, but you better have good specs so you get good performance. I recommend using parsec with a VM if you can passthrough a seperate GPU otherwise. https://github.com/Fmstrat/winapps

The aim of this exercise was to test run WinApps (https://github.com/Fmstrat/winapps).