.NET Framework 1.1, released on 2003-04-24.
The application that required .NET 1.1 Framework installed and ran successfully.
.NET Framework Setup Verification Tool from Aaron Stebner (Microsoft) which checks for proper installation of .NET assemblies and registry entries reports success.
What does not
What was not tested
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Current||Fedora 19 x86_64||Dec 26 2014||1.7.33||Yes||Yes||Gold||Anastasius Focht|
|Show||Ubuntu 14.04 "Trusty" i386 (+ variants like Kubuntu)||Mar 18 2014||1.7.14||Yes||Yes||Gold||Brandon|
|Show||Gentoo Linux x86_64||Aug 20 2013||1.7.0||Yes||No||Garbage||leonice|
|Show||Fedora 18 x86_64||May 25 2013||1.5.31||Yes||Yes||Gold||Anastasius Focht|
|Show||Fedora 16 x86_64||Dec 21 2012||1.5.20||Yes||Yes||Gold||Anastasius Focht|
|Bug #||Description||Status||Resolution||Other apps affected|
|5358||.NET 1.1's dotnetfx.exe fails to install||CLOSED||FIXED||View|
|7098||msi doesn't publish/install some assemblies into GAC||CLOSED||FIXED||View|
|10134||regtlib.exe from .NET 1.1's dotnetfx.exe installer crashes with heap problem||CLOSED||FIXED||View|
|11742||Small .net 1.1 app (FastMD5 1.3) fails to start up||CLOSED||FIXED||View|
|12099||.NET Framework 1.1 installer requires loadperf.dll in case of AeDebug -> Auto=0 (unhandled exception dialog)||CLOSED||FIXED||View|
|13995||Microsoft .NET Framework 1.1 Service Pack 1 fails to install (crash)||CLOSED||FIXED||View|
|15748||.NET 1.1's dotnetfx fails to install, aborts when it can't stop the msi service?||CLOSED||FIXED||View|
|16626||NBC Direct installer can't find resources||CLOSED||FIXED||View|
|16956||Lexware: Installation of .Net 2.0 SP 1 fails||CLOSED||FIXED||View|
|17008||MS .Net Framework 1.1 SP1 installer fails sometimes with "nested exception on signal stack"||CLOSED||FIXED||View|
|17135||virtual write watches cause problems in multithreaded .NET code (simultaneous GC heap allocations)||CLOSED||FIXED||View|
|17161||Provide lodctr.exe tool to prevent misleading process spawn failure console messages (.NET installers)||CLOSED||FIXED||View|
|17184||Achieve Planner 1.9.0 requires explicit native override of mscoree.dll||NEW||View|
|23213||.NET Framework 1.1 installation fails with builtin msvcr71 (unimplemented function _set_security_error_handler)||CLOSED||FIXED||View|
|25120||Microsoft .NET Framework 1.x installer fails with 'CLR error: 80004001' (1.0) or 'Failed to delay load library mscorlib.dll' (1.1) (fusion.CreateApplicationContext is a stub)||NEW||View|
|27199||MS .Net Framework 1.x Service Pack installers crash in InstallFiles action (cabinet stream handling)||CLOSED||FIXED||View|
|39613||Microsoft .NET Framework 1.1 fails to install with Wine 1.3.2+||CLOSED||FIXED||View|
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
ÂÂÂMake sure you operate on a clean 32-bit WINEPREFIX (~/.wine)!
Method 1: Installation by using 'winetricks' script
Use Âthis option for easy installation of .NET 1.1 Framework.
ÂWinetricks will take care of all needed installation prerequisites and worÂk around some problems.
Method 2: Manual installation
Run the installer of .NET Framework 1.1
Optionally install corefonts (using winetricks)
If you intend to use .NET 1.1 Framework without upgrading to .NET 2.0 or later you might need to set a load-order override of "mscoree.dll" library (system32) to "builtin" only (using winecfg).
This is due to different loader implementation between .NET 1.1 and 2.x (or later), see bug 17184Â for explanation.ÂÂ
Use this option for easy installation of .NET 1.1 Framework Service Pack(s).Â
Winetricks will take care of all needed installation prerequisites and work around some problems (.NET 1.1 already installed, Service Packs already applied...).
.NET Framework 1.1 Service Pack 1:
There is no need to manually install .NET Framework 1.1 beÂÂfore. Winetricks does this as part of service pack install!ÂÂÂ
Example command lines you can use to perform unattended installations for the Â.NET Framework 1.1 installationÂ: Â
These command lines will run the .NET Framework 1.1Â setup in fully silent mode. The setup package will extract to a temporary location and installation will begin with no user interaction and no visible UI. The user will see no visible indication that setup is running.
Standard unattended installation
These command lines will run the .NET Framework 1.1 setup in standard unattended mode. The setup package will extract to a temporary location and installation will begin with no user interaction. A progress dialog will appear on the screen during installation, and it will disappear when setup is complete. Errors encountered during installation might pop up message boxes during installation if they occur.
Unattended installation with no cancel button available in the UI
These command lines will run the .NET Framework 1.1 setup in unattended mode with no cancel button. The behavior of setup is the same as with the command lines above except the cancel button will be hidden on the progress page during installation. This allows the user to know that a setup is in progress but prevent them from cancelling it (unless they kill the process).
Last update: 2019-01-06
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://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.
This is bug 25120. You need to set "fusion" component to "native".
Either use 'winecfg' tool or start the installer as follows (if you don't use winetricks recipe):
$ WINEDLLOVERRIDES=fusion=n wine ./dotnetfx.exe
If you get a message box telling:
Failed to delay load library mscorlib.dll (Win32 error: 0).
This program can no longer run and will now terminate.
This is bug 25120
Use winetricks for installation.
URL_ParseUrl FIXME messages on console when running/installing .NET apps are harmless and can be safely ignored. Example console output:
If you see an error message at the end of the installer in console likÂe this:
This message is harmless and expected (see my comment here).