Wine-Mono Isn't Too Fit For .NET

Posted by Michael Larabel on February 04, 2013

Over the past few months there's been several Phoronix articles about Wine-Mono, a fork of Mono and a Win32 build of this open-source Microsoft .NET implementation for Wine. Wine-Mono can be used in place of Microsoft's official .NET framework when it's needed as a dependency for Windows programs running within Wine. Unfortunately, Wine-Mono doesn't always work out well.

Wine-Mono was talked about at the FOSDEM 2013 meeting in Brussels this past weekend in a presentation by Vincent Povirk. Wine-Mono is a specialized upstream Mono code-base that tries to avoid differences with upstream while also being a build for Windows itself -- upstream Mono hasn't been too interested in Mono on Windows but rather for Linux, various mobile operating systems, and other platforms. Wine can't use the Linux version of Mono because it needs to call back into Wine. This specialized Mono build also has registry keys and files for preventing programs from using/installing the native Microsoft .NET run-time. This forked version also bundles in some projects not directly in the Mono code-base, such as some VB class files.

Problems for some Wine users with using the official Microsoft .NET implementation is that its End-User License Agreement requires a Windows license to install .NET, .NET can't be used for porting applications also due to EULA restrictions, and there's a few rare cases where Wine-Mono happens to work better than .NET.

Unfortunately, Wine-Mono doesn't have a vibrant active developer community and its lead developer doesn't expect to achieve much success in the years ahead. "At the rate I'm getting work done, I don't expect much improvement in the next few years."

"I spend more time debugging than making useful changes... It's sort of discouraging," Vincent Povirk added. he also said that he's been overwhelmed by the size and scope of .NET and Mono. In the end the FOSDEM 2013 presentation on Wine-Mono came down to a cry for help in an attempt to attract more development attention to Wine and Mono.

Discuss this article in our forums, IRC channel, or email the author. You can also follow our content via RSS and on social networks like Facebook, Identi.ca, and Twitter (@Phoronix and @MichaelLarabel). Subscribe to Phoronix Premium to view our content without advertisements, view entire articles on a single page, and experience other benefits.
Latest Hardware Reviews
  1. Sumo Lounge Emperor
  2. Gallium3D Continues Improving OpenGL For Older Radeon GPUs
  3. 15-Way Open vs. Closed Source NVIDIA/AMD Linux GPU Comparison
  4. Nouveau vs. NVIDIA Linux Comparison Shows Shortcomings
Latest Software Articles
  1. The Cost Of Ubuntu Disk Encryption
  2. Btrfs vs. EXT4 vs. XFS vs. F2FS On Linux 3.10
  3. AMD Radeon R600 GPU LLVM 3.3 Back-End Testing
  4. F2FS File-System Shows Regressions On Linux 3.10
Latest Linux News
  1. QEMU 1.5 Supports VGA Passthrough, Better USB 3.0
  2. Handbrake 0.9.9 Supports OpenCL Offloading
  3. Freedreno Gallium3D Now Banging The Adreno A3XX
  4. Jolla Announces Their First Phone
  5. Mageia 3 Released, Still Using Legacy GRUB
  6. NetBSD 6.1 Brings In More Features
  7. Using Six Monitors With AMD's Open-Source Linux Driver
  8. Benchmarking The Intel P-State, CPUfreq Changes
  9. FreeBSD Still Working On Next-Gen Package Manager
  10. DNF Still Advancing As Experimental Yum For Fedora
  11. Logitech Begins Supporting Linux Users
Latest Forum Talk
  1. Jolla Announces Their First Phone
  2. Ubuntu To Look At Replacing Firefox With Chromium
  3. What Would You Like To See Next?
  4. Mageia 3 Released, Still Using Legacy GRUB
  5. QEMU 1.5 Supports VGA Passthrough, Better USB 3.0
  6. FreeBSD Still Working On Next-Gen Package Manager
  1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Motherboards
  5. Peripherals
  6. Processors
  7. Software
  8. Operating Systems
  9. All Articles
  1. Linux Benchmarking
  2. OpenBenchmarking.org
  3. Phoronix Test Suite