.NET Framework

What works

Installation(32-bit)

Verification with dotnet verifier

What does not

Workarounds

What was not tested

Installation (64 bit)

Running apps

Hardware tested

Graphics:

• GPU:
• Driver:

Additional Comments

A clean WINEPREFIX was used with only gecko installed(no mono). winetricks was NOT used. Installer was executed manually.

Install winetricks (more details here) to make easier to configure the Wine prefix:

$ sudo wget 'https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks' -O /usr/local/bin/winetricks
$ sudo chmod +x /usr/local/bin/winetricks

Last update: 2020-05-03

As usual, create a new Wine prefix (for most applications, it's better to set its own prefix):

$ env WINEPREFIX=$HOME/winedotnet wineboot --init

If Wine prompts for installing Mono, click Cancel.

Install .NET Framework (and optionally install corefonts):

$ env WINEPREFIX=$HOME/winedotnet winetricks dotnet20 corefonts

Replace dotnet20 with dotnet20sp1 or dotnet20sp2 to install Service Pack 1 or Service Pack 2, respectively.

Use the following command to manually trigger GAC rebuild after .NET Framework installation (or if the Wine prefix changed due to a Wine update):

$ env WINEPREFIX=$HOME/winedotnet wine "c:\\windows\\Microsoft.NET\\Framework\\v2.0.50727\\ngen.exe" update

Some errors (while loading dependent modules that are not GAC'd yet) are expected and can be ignored.

Last update: 2023-06-16

To verify .NET Framework installation(s) you can use the .NET Framework Setup Verification Tool from Aaron Stebner (Microsoft) which checks for proper installation of .NET assemblies and registry entries:

$ wget 'https://web.archive.org/web/20200729095123/https://msdnshared.blob.core.windows.net/media/2018/05/netfx_setupverifier_new.zip'
$ unzip netfx_setupverifier_new.zip
$ env WINEPREFIX=$HOME/winedotnet wine ~/netfx_setupverifier.exe

Select the .NET Framework version you want to verify and evaluate the log file manually if verification failed.

URL_ParseUrl FIXME messages on console when running/installin�g .NET apps are harmless and can be safely ignored. Example console output:

If you see an error message at the end of the installer i­n console like this:

This message is harmless and expected (see my comment here).

This is because you are running the 32-bit installer in a WoW64 Wine. ­There are two ways to overcome this:

Method 1: create 32-bit WINEPREFIX

Set environment variable "export WINEARCH=win32", create a new WINEPREFIX and run the installer

Method 2: "hack" to force install into 64-bit WINEPREFIX

It is possible to install 32-bit .NET Framework in 64-bit prefix (shared Wow64 enviroment):

In order to do this: run the .NET installer as follows:

It will ask you for a folder to put extracted files in. After extraction, go to the folder and open up the "install.ini" in text editor.

Change the value under [setup] section:

to

Now you are ready to run the installer using:

This is only for experts and not the recommended way. Use at own risk! ­

If a .NET application exits with the following mes­sage in console:

This 'Fatal Execution Engine Error' (80131506) is pretty general and can be caused by many things, for example by bug 10506.­

If you get a crash/backtrace like this in console:

Please read appdb entry HOWTO more carefully! This is bug 10467.

If you followed appdb HOWTO and this problem still occurs you most likely have a corrupted "l_intl.nls" file in your winetricks cache. Update your winetricks script to newer version (contains checksum for detection of corrupted download) or remove "l_intl.nls" from "dotnet20" folder in "winetrickscache" and repeat the winetricks step.

­Reported in Bug 16258. It seems the PE image generator runs out of file descriptors while writing out native images. T­his is a bug in the Microsoft .NET 2.0 Framework. Use the following workaround if you encounter this bug:­