How to install Mono or dotNET45 on Linux - Tutorial

For me it wants to downgrade the mono: The Mono version installed on Mac may not be compatible with this version of Visual Studio. Would you like us to install Mono '6.8.0.99' for you? This will overwrite any existing Mono installation on your Mac. The Mono on my Mac is: Mono 6.8.0.123 (2019-10/1d0d939dc30) (64-bit) So, it wants to replace 123. Install Terminal on Mac OS. The client terminal can be installed and run on computers with Mac OS using Wine. Wine is a free software that allows users of the Unix-based systems to run an application developed for the Microsoft Windows systems. Among all the Wine versions there is one for Mac OS. The resulting executable is self contained and does not need the Mono runtime installed to run. However, if your application relies on libraries linked to by the mono runtime or Gtk#, those will need to be installed (Gtk# helper libraries come to mind). Do the following to install wine-mono: Download wine-mono.msi from the official WineHQ site. Type wine64 uninstaller. Press install from the uninstaller GUI and select the downloaded.msi package.

Updated: May 20, 2019

Linux. WINE. Interesting use case. As it happens, I was playing with WINE, trying to install some Windows software. Turns out, the particular program is available natively, so no biggie, but occasionally, I am trying this framework, to see if it's made progress in becoming simpler and easier.

On this particular rainy day, I was not having success with Mono, or dotNET if you will. The application couldn't run, because there was Mono missing on my Linux box, but getting it configured correctly was far from trivial. Hence this tutorial. Someone somewhere out there may have an obscure use case, and this little guide shall come handy one day. Or not. After me.

Error that be

Long story short, when you run wine 'program', you get this:

003a:err:mscoree:CLRRuntimeInfo_GetRuntimeHost Wine Mono is not installed

Self evident, no? Well, the solution is to install the complete Mono framework, which is done by specifying the mono-complete meta package. I tested this on an Ubuntu-based system, so don't hate me if the naming convention is different in your distro:

sudo apt-get install mono-complete

Alas, this did not help.

Solution 1: Official Mono installer

You can grab the package from the official WINE website, and then install it using the Add/Remove functionality via wine uninstaller as I've shown you a few weeks back. Select Add, select the Mono MSI package, and that should be all.

In my case, I did make progress, but not enough. A new error message:

002f:err:mscoree:LoadLibraryShim error reading registry key for installroot

Solution 2: Winetricks

I decided to go old school and fall back to this neat little wrapper script, which you can use to install tons of common Windows applications, libraries and utilities, and hopefully, not have to deal with any fancy errors. I installed the script from the repos, and then installed dotNET 4.5 using it.

sudo apt-get install winetricks

winetricks dotnet45

The UI launched, and I started clicking buttons. Progress was made. Errors came up, but the wizard did not crash. The errors are far from helpful, and unless they block the installation, they should not be shown.

It was a little protracted, and several Microsoft wizards popped up, asking me to accept EULA and such. But in the end, I had dotNET correctly installed - and more importantly - the Windows application was able to detect the framework, and I was able to complete the WINE installation.

If you're wondering, my test program was KeePass, which is also available through the repos. But as it happens, the Windows versions comes with a nicer icon and better system area integration, at least in Plasma, but the UI itself is more visually pleasing natively, possibly due to font DPI and whatnot. So overall, I was rather happy, as usually, I had little luck with WINE attempts in the past.

Conclusion

Here we go. Success! Now, this does not mean we're now in the golden age of Windows-Linux compatibility. Not at all. But every little bit of progress we make is good and useful, especially if it helps people gain more freedom in their software choice. Native solutions are always the best option, but if there ain't one, you can dabble in WINE.

The big issue with this framework is that there's no golden formula. You can't just say, do these four steps and all your applications will install and run well. Nope. There's a fair amount of chance and luck, and some of the setups can be quite convoluted. I guess this one ranges midway on that scale. But we've accomplished our task. You wanted Mono, you got Mono. Happy Linuxing. I mean Winduxing.

Cheers. Foundations of business 5th edition pdf.

Mono is an open-source and cross-platform implementation of the .NET Framework. Wine can use a Windows build of Mono to run .NET applications.

1Installing

Installing

From source

From a source tree, you can use the 'make dev' target to build Wine Mono and configure the current Wine prefix (default or as set by the WINEPREFIX environment variable) to use the build. The 'make dev-setup' target will just configure the Wine prefix without building.

Shared Install

For packagers, and users with multiple prefixes, a shared install is recommended.

To create a shared install, download the appropriate binary tarball from https://dl.winehq.org/wine/wine-mono/ (or build it from source with 'make bin') and extract it to the appropriate location.

Wine will search for Wine Mono in the following places (replacing 5.0.0 with the expected version):

c:windowsmonomono-2.0. Extracting a tarball here is not recommended. If you want to install into a specific prefix, use the Prefix Local Install instructions below. It's only included in this list to make it clear that an installed .msi takes priority over the other loctions.
The directory specified in HKEY_CURRENT_USERSoftwareWineMono string value 'RuntimePath'.
${prefix}/share/wine/mono/wine-mono-5.0.0 or ${builddir}/./mono/wine-mono-5.0.0
/usr/share/wine/mono/wine-mono-5.0.0
/opt/wine/mono/wine-mono-5.0.0

When using a shared install, The 'Wine Mono Windows Support' package must still be installed in the prefix. This is handled automatically on prefix update, so normally it shouldn't be a problem, but in some corner cases you might have to run 'wineboot -u' to set this up after creating the shared install.

Prefix Local Install

How To Install Wine-mono

Wine will automatically download and install the appropriate Wine Mono MSI on prefix update, so this shouldn't usually be necessary.

If you wish to use a different MSI installer than the one you'd get automatically:

Obtain the MSI file you wish to use, either from https://dl.winehq.org/wine/wine-mono/ or by running 'make msi' in a build tree. It's possible you already have the one you want in ~/.cache/wine.
Run 'wine uninstaller' and remove 'Wine Mono Runtime' and 'Wine Mono Windows Support' if you have them.
Run 'wine msiexec /i path/to/wine-mono.msi'

Versions

Wine Version	Wine Mono Version
6.6	6.1.1
6.2	6.0.0
5.19	5.1.1
5.11	5.1.0
5.7	5.0.0
4.20	4.9.4
4.17	4.9.3
4.14	4.9.2
4.11	4.9.0
4.7	4.8.3
4.6	4.8.1
4.3	4.8.0
4.0-rc6	4.7.5
3.13	4.7.3
2.14	4.7.1
2.4	4.7.0
2.0-rc1	4.6.4
1.9.12	4.6.3
1.9.8	4.6.2
1.9.5	4.6.0
1.7.37	4.5.6
1.7.32	4.5.4
1.7.7	4.5.2
1.5.16	0.0.8
1.5.5	0.0.4

Building

For build instructions, see the readme at https://github.com/madewokherd/wine-mono

Debugging

As of Wine Mono 0.0.4, the WINE_MONO_TRACE environment variable may be set as follows to trace calls wit

Wine Mono Is Not Installed Mac