to edit the settings file to reflect deployment locations

1. open the file settings.ini in a text editor such as notepad.
2. find the msi=mysetup.msi entry and replace the default path with the path to your .msi file. for example, if mysetup.msi is located on the local computer in the same folder as setup.exe, the path will be msi=mysetup.msi. if mysetup.msi is located on a network share in a folder named myprojectfolder, an example of the path is msi=\\mynetworkshare\myprojectfolder\mysetup.msi. if mysetup.msi is located in a folder named myinstallerfiles, on the same cd as setup.exe, an example path is msi=myinstallerfiles/mysetup.msi.
3. find the fxinstallerpath=c: entry and replace the default path with the correct path to the .net framework redistributable package, dotnetfx.exe. for example, if dotnetfx.exe is located on the local computer in a folder named myprojectfolder, the path will be fxinstallerpath=c:\myprojectfolder\. if dotnetfx.exe is located on a network share in a folder named myprojectfolder, an example of the path might be fxinstallerpath=\\mynetworkshare\myprojectfolder\. if dotnetfx.exe is located in a folder named myexecutables, on the same cd as setup.exe, an example path is fxinstallerpath=myexecutables/.
4. save the settings.ini file.

the setup.exe bootstrapper sample performs a comparison between the build number of the .net framework installed on the target computer and the build number of the .net framework being hosted by the application to install. if there is not a matching build number, setup.exe installs the version of the .net framework being hosted by the application. if you want setup.exe to check for a build number and language version of the .net framework, you must specify the language to check for in the settings.ini file. if you do not specify a language for the languagedirectory variable, setup.exe checks for the english language version by default.
the following table lists the available language versions and the culture name to specify in the settings.ini file.

to edit the settings file to check for a language version

1. open the file settings.ini in a text editor such as notepad.
2. find the languagedirectory= entry. uncomment the entry and specify the correct language version to check for. for example, if you want setup.exe to check for the french language version of the .net framework, specify languagedirectory=fr.
3. save the settings.ini file.

installing localized versions of dotnetfx.exe

dotnetfx.exe has been localized into eight languages. for a complete list of available languages, see the table in the previous section. you can download the localized versions of dotnetfx.exe from the download center or the microsoft windows update web site.
when installing the .net framework redistributable package, dotnetfx.exe, on a computer running the windows® 98 operating system, you must install the localized version of dotnetfx.exe that corresponds to the localized version of windows 98 running on the computer. for example, you must install the german version of dotnetfx.exe on a computer running the german version of windows 98. this limitation only applies to windows 98. you can install any language version of dotnetfx.exe on any language version of windows me, windows 2000, windows nt® 4.0, windows xp, or the windows .net server family.

minimum configuration requirements

this section describes the minimum configuration requirements for a computer where the .net framework redistributable package is to be installed. if the minimum operating system and software requirements are not met, dotnetfx.exe setup will block the installation of the redistributable package. specifically, note that you cannot install the .net framework redistributable package on a computer running the microsoft windows 95 operating system.

platform and software requirements

minimum requirements

to install dotnetfx.exe, you must have one of the following operating systems with microsoft internet explorer 5.01 or later installed on your computer:

• microsoft windows 98
• microsoft windows 98 second edition
• microsoft windows millennium edition (windows me)
• microsoft windows nt 4 (workstation or server) with service pack 6a
• microsoft windows 2000 (professional, server, or advanced server) with the latest windows service pack and critical updates available from the microsoft security web site.
• microsoft windows xp (home or professional)
• microsoft windows .net server family

caution   if you install dotnefx.exe on windows .net server beta 3, you will break the version of the .net framework that is installed with the operating system. windows .net server beta 3 installs version 1.0.3215 of the .net framework. if you install a later version of the .net framework, version 1.0.3215 will be broken. if you install a later version, you can run and use the later version. however, you will not be able to use version 1.0.3215, even after uninstalling the later version.

recommended software

depending on your application requirements, you might also need to install one or more of the following:

• mdac 2.6 or later for data access, available from the universal data access web site.
• core wmi for windows instrumentation, available from the download center.

note   if the recommended software requirements are not met, setup will not block installation or warn you of their absence.

recommended server software

depending on your application requirements, you might also need the following server software:

• mdac 2.7 for data on the server, available at the universal data access web site.
• internet information services (iis) on the server for windows 2000, windows xp (professional), and windows .net server. this is required for using asp.net applications.

hardware requirements

minimum hardware requirements

* or the minimum cpu required to run the operating system, whichever is higher.
** or the minimum ram required to run the operating system, whichever is higher.

recommended hardware