• Install Wine Mono Machines
• Install Wine Mono Macbook
• Install Wine Mono Mac And Grill
• Wine Mono Download

Information about running AWB on Mono/Wine.

Mono[edit]

Status: Not yet usable for general use.

• See http://tools.wmflabs.org/awb/mono/output.html
• AWB can be built under mono, but raises exceptions at runtime during load, and does not open cleanly.

Mono setup[edit]

Nov 26, 2018  SUBSCRIBE: DOWNLOAD link to Wine Mono: Commands used: 1. Sudo apt-get install winetricks 2.

Install Mono on macOS. Mono runs on Mac, this page describes the various features available for users who want to use Mono or Mono-based technologies on macOS. Installing Mono on macOS is very simple: Download the latest Mono release for Mac. Run the.pkg file and accept the terms of the license. Wine is capable of running some winforms-based Windows applications on Mac OSX. When it works as intended, all you have to do is install Wine on the Mac, and then it can run your exe. Of course this won't always work perfectly, and it won't have the polish of a native. How to Download Wine on a Mac. RELATED: 5 Ways to Run Windows Software on a Mac There are several ways to get Wine on a Mac. The official project website at WineHQ now provides official builds of Wine for Mac OS X. However, those aren’t necessarily the best option.

Mono install (Linux)[edit]

• Get the packages/see the official guide at the Mono downloads page
• Be sure to install mono, monodevelop, mono-devel, mono-nunit and any other packages for dependencies
• perl is required for the build event to set the SVN revision number.

Mono install (macOS)[edit]

• Read the guide, and install MonoDevelop. Be sure to have MDK.
• Stop right here -- There's no libgluezilla. You can try compiling the lib for macOS. MonoMac or Monobjc may be a solution, still.

Building AWB[edit]

• To run AWB under wine you must build under Mono version 3 (3.8 works). Mono version 4 enforces use of .NET 4 libraries that wine isn't happy with.
• Open the AutoWikiBrowser no plugins project solution
• Manually create the SvnInfo.cs file in WikiFunctions directory (copy the SvnInfo.template.cs file, write the version code if you want to).
  • An incomplete shell version of SubWCRev: http://stackoverflow.com/questions/1954062/emulate-subwcrev-when-using-git-svn
• If build fails due to WikiFunctions pre-build event, edit WikiFunctions.csproj to delete the text within the PreBuildEvent tags (at the end of the file)
• rev 8712 and earlier: Make a change to the end of Resources.resx to fix the build error, then AWB will build (AWB rev 7686, opensuse 11.4 64-bit, MonoDevelop 2.4.2)
• rev 8966 and later: download Microsoft.mshtml.dll and add a reference to the file in the AutoWikiBrowser project. Ensure the dll is placed alongside AutoWikiBrowser.exe when you run it.

• Hint: Always try the Unit tests. Under Mono 3.8 around 5 sets of unit tests fail due to mono issues. Under Mono 4.2 all unit tests pass correctly.
• If at runtime under Wine you get errors relating to System.Drawing version 4.0.0.0, disable the “use msbuild” option for WikiFunctions and AutoWikiBrowser projects in MonoDevelop and rebuild. If the build then fails due to missing .resources files, remove the obj directory in AWB/AWB/ (per MonoDevelop bug note) and rebuild.

Running under mono[edit]

• Disabling a couple of references to webbrowser in Main.cs will allow AWB to open cleanly (Mono 3.8 or Mono 4.2). Things such as list comparer, list filter, database scanner (Mono 3.8 gives error on large files, Mono 4.2 works cleanly) can be used.
• The web browser component is not working. Installing libgluezilla does not work as libgluezilla gives a stack trace.
  • Therefore cannot view diff or preview when editing pages.

Running unit tests (for developers)[edit]

• Mono: Running unit tests under Mono using MonoDevelop all pass correctly with Mono 4.2.2 and rev 11894. With Mono 3.x some unit tests incorrectly fail.
• NUnit via Wine Running unit tests using NUnit through wine works, all tests run and pass successfully, as of AWB rev 10524.
  • Download pre-compiled Windows binaries (zip) from NUnit website
  • Run using wine nunit-x86.exe, open the UnitTests.nunit file.

Wine[edit]

Status Known to be generally working.

• See Wine AppDb entry for AWB

Setup and installation[edit]

Getting Wine and Winetricks[edit]

Ubuntu/Mint[edit]

1. Install Wine. Use the package installation tool of your choice, such as apt-get. If you prefer, direct downloads of Wine are here.
2. Install Winetricks using the same installation tool. You'll need this to install additional components and DLLs used by AWB. Some distributions of Wine include Winetricks; others do not. For more information, see the Winetricks on the Wine wiki.

Fedora[edit]

1. Install Wine by running command sudo yum install wine
2. Install Winetricks by running command wget http://winetricks.org/winetricks && chmod +x winetricks

openSUSE[edit]

Just install wine and winetricks and any required dependencies via YaST/zypper.

Arch Linux[edit]

Ensure the multilib repository is enabled by uncommenting or adding the following lines in /etc/pacman.conf:

Then, install wine and winetricks: pacman -S wine winetricks

macOS[edit]

1. If you don't have X11 installed (check by trying startx), install a working X11 environment from XQuartz.
2. Use your package manager to install wine. If you don't have a package manager, consider using Homebrew:
   1. Head to brew.sh, and follow its instructions for installing Homebrew.
   2. Run brew install wine to download and install wine. Append --devel for new bugfixes and potentially new bugs on the development branch. Read brew info wine for informations and suggestions.
3. Install Winetricks by running command curl http://winetricks.org/winetricks > winetricks && chmod +x winetricks.

Setting up the Wine environment[edit]

1. If your Wine environment is 64-bit (it is by default on 64-bit machines), you'll need to reconfigure it to 32-bit as .NET 2.0 requires a 32-bit environment. Use Terminal (i.e. the command-line) to adjust the WINEARCH variable by running the command WINEARCH=win32 winecfg. See this wiki section for more information. If you get the wine: WINEARCH set to win32 but '[PATH]' is a 64-bit installation. message, choose a different prefix in that previous command, or if this is your first time using WINE, delete the .wine folder specified by the path, then run the command again. This will recreate the Wine prefix with a 32-bit environment (i.e. WINEARCH=win32 WINEPREFIX=~/.local/share/wineprefixes/dotnet35 winetricks dotnet35).
2. Use Winetricks to install dotnet35. You can use the Winetricks GUI to do this, although it can also be done in the command-line (winetricks dotnet35). This may require manual downloads, and make sure that all the required components are actually installed: you may need to rerun Winetricks to finish the installers.
   • .NET 4.5: with wine 1.7.39 and winetricks from March 2015, .NET 4.5 will install correctly. AWB appears to run fine under this .NET version as well.
   • November 2019 / TLS 1.2: from November 2019 it appears that Wikipedia requires HTTPS TLS 1.2 for connectivity, a known working setup for this is wine 4.19 and winetricks dotnet462 (wine 3.7 and dotnet462 did not work). If you're using an older Ubuntu/Debian package, you may need to get a newer version of winetricks otherwise it may fail to download the necessary files.

Starting AWB[edit]

1. To start AWB, run command wine 'path/to/AutoWikiBrowser.exe', putting the location of AutoWikiBrowser in the quotes.

• AWB should be working, though there is a glitch in the diff view that is fixed by installing Internet Explorer. IE6 or IE8 have both been confirmed to be sufficient. As of September 2015, IE7 is the only version working well. Use winetricks ie7 to install it, and avoid installing IE8, as it would render AWB unusable.

Wine AppDb entry for AWB[edit]

Please update this page or the Wine AppDb entry for AWB with further information on your experience.

What works[edit]

• Open AWB
• Open Settings, save settings
• General fixes, typo fixing, TypoScan plugin
• Edit box, diff (with winetricks ie6), preview
• Save pages
• List comparer, list splitter
• List providers (searches)
• Custom modules
• External processing
• Logging

Known problem areas[edit]

• Database scanner, often fails after a few minutes or seconds before the scan has completed (with error 'No access to memory location', Wine bug 40156). No current known workaround or solution for Wine. Database scanner works with wine 3.5 and winetricks dotnet40, was not working with wine 2.0.1 or earlier. Database scanner also works under Mono 4.2.
• Find match/error/syntax highlightingwinetricks riched20 fixes this.
• Tooltips
  • Focus change: AWB 5.6.0.0 and earlier, up to SVN 11269: Tooltips can cause application focus to switch to the tooltip (could be Wine bug 9512). Workaround: in wine config, Graphics section (winecfg) uncheck 'Allow the window manager to control the windows' and restart AWB, tooltips will then display without stealing focus, but this will mean AWB window isn't integrated with your system's window manager. Workaround implemented in AWB in rev 11270 and later, display of tooltip does not affect application focus.
  • Caching: there can sometimes be a caching/lag issue whereby tooltips fail to display the first time, or are shown once when they should not be. Focusing on another item that does have a tooltip generally causes the tooltip display to move on or catch up. No current known workaround or solution.
• External Processing: in rev 11780 and earlier scripts may not work under Wine. Alternative solutions to running unix scripts with AWB. From rev 11780 scripts work using full Linux paths.

Tips & tricks[edit]

• You may get more frequent connection errors, especially on login/the first save, but just try again.
• If you sometimes encounter the exception 'attempted to read or write protected memory' and the wiki page you are processing has some Latin extended Unicode characters in it, change AWB's edit box font away from the Tahoma default to another TrueType font e.g. one of the Liberation sets. This should prevent the exception.

Wine on a Mac using homebrew[edit]

AWB can be installed to run under Wine on a Mac using the Homebrew package management software. It may be possible using other package management systems like Fink, Gentoo/Alt, MacPorts, Pkgsrc or Rudix. See the main WineHQ - macOS page.

• Install Homebrew.

• Or update homebrew and its formulas, if you already have Homebrew.

brew update

• You may need to install XCode for brew to work fine and install the XCode command line tools. The brew installer will ask you to do so automatically.

xcode-select --install

• Check for problems.

brew doctor and just in case, you may want to do it again: brew doctor

• Make sure you have X11.

Run startx. If there’s a “command not found” error—or similar—then you probably need an X11 client. Try XQuartz if you’re not sure which one to use: http://xquartz.org

• Install wine and winetricks: brew install wine winetricks
  • Sometime the dependancies of wine may need to be reinstalled, systems older than OS X 10.9 may need them installed with the --universal option. e.g.

• Sometimes you may want to change how the fonts are rendered so they look better. See manpage: fonts-conf for rendering stuffs and wine winecfg for changing the DPI setting of wine. — Preceding unsigned comment added by 222.65.178.5 (talk) 09:04, 11 September 2014 (UTC)

• Install .NET Framework 3.5 in wine, following the steps in #Setting up the Wine environment.
  • It may fail on wine msiexec /i XPSEP XP and Server 2003 32 bit.msi. Don't worry.
  • If the installation looks like it got stuck the window might just be hidden. Click on the icon in the menu bar to bring it back to foreground and confirm the dialog to continue.

• Run AWB

wine AutoWikiBrowser.exe

• AWB runs fine but does not clear the diff window so you will need to scroll to the bottom of the page.

CrossOver[edit]

Wine's commercial version, CrossOver, has good and easy support for AWB. It works under Linux and Mac. (A free trial is available for 14 days.)

• Download and install the trial version from https://www.codeweavers.com/products.
• Install the .NET Framework 3.5 SP1 choosing Windows Vista or later
• Run Command, browse to the AutoWikiBrowser.exe. Click Run.

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.

Installing

For Wine releases 1.5.3 and later, the Wine-Mono package is recommended. For earlier versions, an official Windows release of Mono 2.10 is recommended.

Wine 1.5.6 and later will install Wine-Mono automatically as needed. It will search for the MSI in the following locations:

• The Unix directory stored in the 'MonoCabDir' value at HKCUSoftwareWineDotnet.
• /usr/share/wine/mono, or possibly some substitution for /usr if Wine was installed to a different location.
• wine_build_directory/./mono, if Wine is being run from a build tree.
• Download from http://dl.winehq.org/wine/wine-mono/.

Unlike gecko, there is only one package containing the code for both x86 and x86_64, as most of the code does not depend on the architecture.

The Mono package should always be removed before installing native .NET. This can be done with the following command-line:

In a 64 bit wineprefix, substitute wine64 for wine in the above command

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 within Mono:

This option is the same as the --trace option in Mono.

Note that 'All assemblies' includes the program itself and all libraries shipped with it. Mono is capable of tracing any .NET code. You probably should avoid the 'all' trace if there might be proprietary code running in the process.

Install Wine Mono Machines

Activating any trace at all, even a bogus assembly name, will cause Mono to print out all exceptions as they occur. This can be useful, but it can also be misleading as some exceptions are perfectly normal.

If you're not sure which libraries might be involved in a problem, and no exceptions are being raised, try WINE_MONO_TRACE=wrapper. It tends to be low-traffic while also containing useful information.

In earlier versions of Wine, the 'MONO_TRACE' environment variable may work.

Virtual DJ Software, MP3 and Video mix software. VirtualDJ provides instant BPM beat matching, synchronized sampler, scratch, automatic seamless loops. Virtual dj controller free download. Jan 22, 2020  Atomix Productions' Virtual DJ Free not only mixes and mashes beats from a classic two-deck console, but also it serves as audio central for your.

If you see 'Stacktrace:' in the console, this means that Mono has crashed. To debug, set MONO_DEBUG=suspend-on-sigsegv. You will then see 'Received SIGSEGV, suspending..' after the crash, and you can attach winedbg to the process.

Documentation

Standard .NET namespaces and classes are documented at MSDN here: http://msdn.microsoft.com/en-us/library/w0x726c2.aspx

Runtime detection

As of 1.3.7, Wine will search for a Windows install of Mono in the following locations:

• c:windowsmonomono-1.0 or mono-2.0
• If Wine is installed, <prefix>/share/wine/mono/mono-1.0 or mono-2.0, where <prefix> is usually /usr or /usr/local.
• If Wine is run from a build tree, wine/./mono/mono-1.0 or mono-2.0
• The path specified in the registry, if Mono was installed via the official Windows installer.

The Wine Mono package installs its files in c:windowsmonomono-2.0. In modern Wine (>= 1.5.6), without Wine Mono installed it will appear to Windows applications that .NET is not installed, so the only real option is to use that package.

Test Suite

See http://www.mono-project.com/Testing first.

Running the Mono test suite on Wine is very important for fixing bugs (in Mono and in Wine), and I suspect that MS .NET hosted in Wine will also benefit from some of the fixes made for the Mono tests.

The Mono build system has make targets for running tests, but using them on Windows or Wine requires building Mono with cygwin or doing strange things to the build system. To make this easier, the build script for wine-mono will create self-contained builds of the Mono test suite when run with the -t switch. These tests are located in directories named like tests-net_2_0.

Install Wine Mono Macbook

To run tests, run nunit-console.exe with the dll file containing the tests as an argument. For example, to run the System.Drawing tests:

Install Wine Mono Mac And Grill

You could also invoke nunit-console.exe using Mono, or on a Windows machine from a command prompt. NUnit is actually a general-purpose unit testing framework for .NET, which Mono happens to use, and it should work on any .NET impelementation.

You can use the /fixture or /run switches to run only a single related set or tests or a single test.

Note that the tests are marked based on whether they are expected to work on various platforms, and running them in this way will include tests that are known not to work in Mono. One would have to use the /exclude switch to change this.

Microsoft .NET

Wine Mono Download

If you need to use Microsoft's implementation of the .NET framework, the Microsoft runtimes can partly run on Wine. You can find tips and share comments with other users at the .NET AppDB page.

You can install the appropriate version of Microsoft's .NET runtime (dotnet35, dotnet30, dotnet20, or dotnet11) through winetricks. Be aware though, that your .NET application still might not work (at least not yet), and Microsoft's .NET runtimes are not free software so be sure to read the EULA before accepting. Mono, on the other hand, is free software, supported by a strong community, and probably a better choice if it works with your application.