wine-mono-4.8.1

Changes since 4.8.0:

• The MSI has been overhauled, and the Wine Mono package has been internally split into 2 parts: runtime and windows support. The runtime contains a complete Mono install and supporting libraries. The windows support package contains the files and registry keys needed to convince Windows programs that .NET is installed. This change should be mostly transparent to the user, but it means you may see two different entries for Wine Mono in the uninstaller list.
• Various updates to account for different install paths.
• Both of those changes combined make it possible to install the runtime, which takes the bulk of the disk space, in a shared location instead of the Wine prefix. Those files are now available in the -bin tarball.
• The fake .NET install has been updated so the real .NET installers existing now shouldn't try to install over Wine Mono anymore.
• FNA has been added along with wrappers to support XNA 4.0 games. For right now, if the XNA redistributable is installed, Wine Mono will try to use that (and fail due to bugs), unless you set WINE_MONO_OVERRIDES=Microsoft.Xna.Framework.*,Gac=n.
• Fixed a build failure when the tarball was used without a network.
• The provided Vagrant build vm will now base its memory and cpu resources on the host machine.
• Fixed a bug where the vtable of the _AppDomain COM interface was incorrect.
• A few minor bug fixes from upstream Mono.

Notes for packagers:

This release adds the ability to install Wine Mono to a shared location, such as /usr/share/wine, as a full directory structure that Wine can use directly. The primary benefit is saved disk space. Wine will no longer need to copy the whole Mono runtime into every Wine prefix.

The old method of placing the .msi in one of the standard locations will continue to work the way it always has, but it will cause Wine to copy the full runtime to every prefix.

Wine Mono can be installed globally by extracting wine-mono-bin-4.8.1.tar.gz to /usr/share/wine/mono or /opt/wine/mono. This will create a directory named, for example, /usr/share/wine/mono/wine-mono-4.8.1. The -bin .tar.gz is created by the normal build process, similar to how the msi is built now. The build process also creates an image/ directory which can be used directly.

When using a shared install, only "Wine Mono Windows Support" will appear in the "wine uninstall" list. "Wine Mono Runtime" will not appear in this case because it doesn't need to be installed to an individual prefix.

Wine's search path for the runtime is as follows:

• c:\windows\mono\mono-2.0 (the path created by the Wine Mono Runtime msi)
• The path specified by a string value named RuntimePath in HKEY_CURRENT_USER\Software\Wine\Mono
• When running from a build tree, build_dir/../wine-mono-VERSION
• INSTALL_PREFIX/share/wine/mono/wine-mono-VERSION
• /usr/share/wine/mono/wine-mono-VERSION
• /opt/wine/mono/wine-mono-VERSION