The Microsoft .NET Framework SDK version 1.1 (released: 2006-11-29)
includes everything developers need to write, build, test, and deploy .NET Framework applications, documentation, samples, and command-line tools and compilers.
What does not
GUI debugger (DbgCLR)
What was not tested
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Current||Fedora 19 x86_64||Jan 10 2015||1.7.34||Yes||Yes||Bronze||Anastasius Focht|
|Show||Fedora 16 x86_64||Mar 08 2012||1.4||Yes||Yes||Bronze||Anastasius Focht|
|Show||Fedora 12 x86_64||Mar 07 2010||1.1.40||Yes||Yes||Bronze||Anastasius Focht|
|Show||Fedora 9||Oct 26 2008||1.1.7||Yes||Yes||Bronze||Anastasius Focht|
.NET Framework 1.1 Redistributables installation is needed as prerequisite. Refer to .NET Framework 1.1 installation HOWTO for installation instructions.
Example command lines you can use to perform unattended installations for the .NET Framework 1.1 SDK installation:
These command lines will run the .NET Framework 1.1 SDK 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 SDK 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 SDK 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).
This is caused by self registration of Microsoft CLR Debugger for first time:
which interacts with MDM (Microsoft Machine Debug Manager) COM Service
The reason of this "hang" is currently unknown.
Either stop the MDM service from another terminal:
or kill the processes using:
Alternatively use one of the unattended install modes from HOWTO which doesn't exhibit this problem.