Hello Jens and Austin, On 2018-10-28 2:36 p.m., Jens Reyer wrote: >>> On 28.10.18 01:22, Alexandre Viau wrote: >> Can you reproduce this? >> >> - rm -rf ~/wine >> - wine explorer >> - browse c:\\windows\mono > > Tested: No, no mono folder at all.
>> It could be that wine picks-up wine-mono from an unknown location on my >> system without me noticing... > > Check for ~/.cache/wine/wine-mono-4.7.1.msi. That will be installed > automatically and result in a full c:\\windows\mono folder. You might > have downloaded it accidentally if you used another Wine (not from > Debian, where we removed the installer download). AHH! I did compile wine from upsteam's sources a few times. It must have downloaded wine-gecko and wine-mono the first time I ran it and /usr/bin/wine must have picked it up from the cache. This definitely explains why I couldn't find apps that didn't run without wine-mono and that ran with it. I **always** has wine-mono installed when testing. Thank you! >>> btw, the command is always "wine" (not wine64 or wine32), e.g. "wine >>> msiexec /i winemono.msi". Wine will then figure out internally which >>> Wine loader to use. This is true both upstream and in Debian. >> >> Sure, I specified wine64 because this is what WineHQ's wiki specifically >> says so, for 64bit prefixes: >> - https://wiki.winehq.org/Mono >> >> It also yields totally different results, if we trust wine uninstaller. >> Note that the .msi is supposed to install both 32 and 64bit versions of >> mono. It could be that installing it with just wine will install only >> the 32bit version and skip the 64bit version. > > Ok, that's new to me. I'd need to look into that more deeply (no > promise, tell me if you need more help). Will do. I'll need to re-evaluate these findings since I might get totally different results now that I removed the wine-mono msi from the cache. I'll also get back to you on whether or not we need to extend the addon patch. On 2018-10-28 2:53 p.m., Austin English wrote:> On Sat, Oct 27, 2018 at 6:22 PM Alexandre Viau <av...@debian.org> wrote: >> Does one of you have happen to know an example of a program that does >> not work using Debian's wine but works when installing the wine-mono >> .msi at: >> - https://dl.winehq.org/wine/wine-mono/ ? > > For testing, using a C# hello world is easy: > austin@debian-desktop:~/debian-mono$ cat hello.cs > // A Hello World! program in C#. > using System; > namespace HelloWorld > { > class Hello > { > static void Main() > { > Console.WriteLine("Hello World!"); > } > } > } > > # Compile it (needs mono-mcs package): > $ mcs hello.cs > > # Then run it. Without mono: > austin@debian-desktop:~/debian-mono$ wine-development hello.exe > 0009:err:mscoree:CLRRuntimeInfo_GetRuntimeHost Wine Mono is not installed > > # With mono: > $ msiexec /i ~/.cache/wine/wine-mono-4.7.1.msi > ... > $ austin@debian-desktop:~/debian-mono$ wine-development hello.exe > Hello World! This will be helpful, thank you! I had been looking for such an application for a while, but the fact that wine-mono was installed by default in my prefixes must have made my research impossible. On 2018-10-28 3:03 p.m., Jens Reyer wrote:> On 28.10.18 19:53, Austin English wrote: >> For testing, using a C# hello world is easy: > [...] > > For completeness, someone else from winehq just told me (and it seems > they would really be happy to see wine-mono packaged as that would > ease their support burden Oh, I'll definitely get this done. It find it very impressive that we can run dotnet apps without Microsoft's implementation, in Wine. Even if the number of apps that work with this are limited, I am happy that we can run them with less proprietary software. > .NET apps that work with wine-mono are mostly older ones (v2.0). The > MS Office 2007 and 2010 installers come to mind. (Note that the Office > 2010 installer doesn't work in current Wine for other reasons.) I might try them out to confirm that Debian's wine-mono build works fine. Cheers, -- Alexandre Viau av...@debian.org
signature.asc
Description: OpenPGP digital signature
