Hello.
Installing Mono (wine-mono-6.4.0-x86.msi) is exactly is same if installing net framework ?
Even with Mono installed on WINE need install net framework to softwares work ?
The install file wine-mono-6.4.0-x86.msi is named about 32 bits. Installing wine-mono-6.4.0-x86.msi run 64 bits exe or only 32 bits ?
Thanks for reply.
Installing Mono need install netframework ?
Re: Installing Mono need install netframework ?
I had posted that thread because see user saying that a software only work if installing net framework.
In wiki the information is mono run net framework 4.x
What is the net framework version 4 ? all versions 4 or only one ?
In wiki the information is mono run net framework 4.x
What is the net framework version 4 ? all versions 4 or only one ?
Re: Installing Mono need install netframework ?
The wiki doesn't say that. What the wiki says is that wine-mono is a replacement for .NET 4.x and earlier, but not for .NET 5.0 and later. It can be installed alongside .NET 5.0 and later, but cannot coexist in the same wineprefix with earlier versions of .NET.In wiki the information is mono run net framework 4.x
- JoseskVolpe
- Level 4
- Posts: 124
- Joined: Sat Sep 04, 2021 9:35 pm
Re: Installing Mono need install netframework ?
Yes and no.... As Dimesio said, Wine Mono is a open-source replacement of Microsoft's .NET Framework. It implements functions from .NET that let them work under Wine without the need to install .NET under Microsoft license. WineHQ cannot provide .NET framework alongside Wine because of the license conflicts. But not only license is the problem, you must install Wine Mono instead on your default prefix because it's prepared to make .NET applications to work out-of-the-box with Wine, and while .NET is installed on special configurations to solve compatibility issues (i'll explain it in the next question), it may experience different issues and bugs on other applications that works just fine with Wine Mono on Wine (and the Wine team cannot solve it so easily with .NET because they don't have access to the source-code).Installing Mono (wine-mono-6.4.0-x86.msi) is exactly is same if installing net framework ?
So installing .NET on Wine is not exactly the same to installing Wine Mono on Wine. You should install Mono.
No.Even with Mono installed on WINE need install net framework to softwares work ?
Wine Mono is a replacement of .NET 4.x.x. While you can install newer .NET versions (5.xx, 6.xx, etc) alongside Mono because it has a different structure from 4.x.x and is open-source (but you don't need it since it is usually integrated into applications), you can't install .NET 4.x.x and earlier alongside Wine Mono. Installing .NET 4.xx without tricks used by winetricks also leads to prefix issues and corruptions.
However, Wine Mono has some functions that were not currently implemented or are experimental. Another applications may not work under Wine Mono and but work better with .NET Framework. If that's your case, you'll need to create a new prefix, install .NET on this prefix with winetricks and run this applications on it. That'll replace Wine Mono on a new prefix and not in your default prefix. You'll only install .NET Framework on cases like this, and use Wine Mono by default.
It'll work just fine. On Windows, some 64-Bits applications also uses 32-Bits libraries, that's the case with .NET 4.x.x.The install file wine-mono-6.4.0-x86.msi is named about 32 bits. Installing wine-mono-6.4.0-x86.msi run 64 bits exe or only 32 bits ?
Your welcome ^w^Thanks for reply.
- JoseskVolpe
- Level 4
- Posts: 124
- Joined: Sat Sep 04, 2021 9:35 pm
Re: Installing Mono need install netframework ?
Also, if another application don't work with Wine Mono and you have to install .NET to make it work, report a bug in bugzilla if it wasn't reported before.
-
- Level 4
- Posts: 149
- Joined: Mon Jun 02, 2008 5:03 pm
Re: Installing Mono need install netframework ?
The x86 package contains both 32-bit (x86) and 64-bit (x86_64) code, so it can run 64-bit programs. Most of the code is CIL (a bytecode that gets translated to the host architecture as needed), so it didn't make much sense to have 2 different packages. I called it "x86" to distinguish it from a possible future arm version.