Dotnetfx45 Full X86 X64 Exe
- Dotnetfx45 Full X86 X64 Exe
- Download Dotnetfx45_full_x86_x64.exe Offline Installer
- Dotnetfx45_full_x86_x64.exe Silent Install
DotNetFx45Fullsetup.exe - Google Drive. Downloads for building and running applications with.NET Framework 4.5. Get web installer, offline installer, and language pack downloads for.NET Framework. Describes the.NET Framework 4.6.2 offline installer for Windows 7 SP1, Windows 8.1, Windows 10 (Version 1507), Windows 10 November Update (Version 1511), Windows 10 Anniversary Update (Version 1607), Windows Server 2008 R2 SP1, Windows Server 2012, and Windows Server 2012 R2. DOWNLOADED 219839 TIMES File Name: dotNetFx40 Full x86 x64.exe 48.11 MB It will only get better! Free ANSWERS and CHEATS to GAMES and APPS.
Wine dotnetfx45fullx86x64.exe. Then you should see the installer manager window. Just follow the prompts and finish up the installation. Important UPDATE! Dotnetfx40 full x86 x64.exe is a type of EXE file associated with STARapp developed by StarApp for the Windows Operating System. The latest known version of Dotnetfx40 full x86 x64.exe is 2013.5.19.1708, which was produced for Windows 8. This EXE file carries a popularity rating of 1 stars and a security rating of 'UNKNOWN'. Download locations for NET Framework 2.0 Final, Downloads: 560475, Size: 22.42 MB. The programming model of the.NET.
This topic provides information for developers who want to install any version of the .NET Framework from .NET Framework 4.5 to .NET Framework 4.8 with their apps.
You can download the redistributable packages and language packs for .NET Framework from the download pages:
Important notes:
Versions of the .NET Framework from .NET Framework 4.5.1 through .NET Framework 4.8 are in-place updates to .NET Framework 4.5, which means they use the same runtime version, but the assembly versions are updated and include new types and members.
.NET Framework 4.5 and later versions are built incrementally on .NET Framework 4. When you install .NET Framework 4.5 or later versions on a system that has .NET Framework 4 installed, the version 4 assemblies are replaced with newer versions.
If you are referencing a Microsoft out-of-band package in your app, the assembly will be included in the app package.
You must have administrator privileges to install .NET Framework 4.5 or later versions.
.NET Framework 4.5 is included in Windows 8 and Windows Server 2012, so you don't have to deploy it with your app on those operating systems. Similarly, .NET Framework 4.5.1 is included in Windows 8.1 and Windows Server 2012 R2. .NET Framework 4.5.2 isn't included in any operating systems. .NET Framework 4.6 is included in Windows 10, .NET Framework 4.6.1 is included in Windows 10 November Update, and .NET Framework 4.6.2 is included in Windows 10 Anniversary Update. .NET Framework 4.7 is included in Windows 10 Creators Update, .NET Framework 4.7.1 is included in Windows 10 Fall Creators Update, and .NET Framework 4.7.2 is included in Windows 10 October 2018 Update and Windows 10 April 2018 Update. .NET Framework 4.8 is included in Windows 10 May 2019 Update. For a full list of hardware and software requirements, see System Requirements.
Starting with .NET Framework 4.5, your users can view a list of running .NET Framework apps during setup and close them easily. This may help avoid system restarts caused by .NET Framework installations. See Reducing System Restarts.
Uninstalling .NET Framework 4.5 or later versions also removes pre-existing .NET Framework 4 files. If you want to go back to .NET Framework 4, you must reinstall it and any updates to it. See Installing the .NET Framework 4.
The .NET Framework 4.5 redistributable was updated on October 9, 2012 to correct an issue related to an improper timestamp on a digital certificate, which caused the digital signature on files produced and signed by Microsoft to expire prematurely. If you previously installed the .NET Framework 4.5 redistributable package dated August 16, 2012, we recommend that you update your copy with the latest redistributable from the .NET Framework download page. For more information about this issue, see Microsoft Security Advisory 2749655.
For information about how a system administrator can deploy the .NET Framework and its system dependencies across a network, see Deployment Guide for Administrators.
Deployment options for your app
When you're ready to publish your app to a web server or other centralized location so that users can install it, you can choose from several deployment methods. Some of these are provided with Visual Studio. The following table lists the deployment options for your app and specifies the .NET Framework redistributable package that supports each option. In addition to these, you can write a custom setup program for your app; for more information, see the section Chaining the .NET Framework Installation to Your App's Setup.
| Deployment strategy for your app | Deployment methods available | .NET Framework redistributable to use |
|---|---|---|
| Install from the web | - InstallAware - InstallShield - WiX toolset - Manual installation | Web installer |
| Install from disc | - InstallAware - InstallShield - WiX toolset - Manual installation | Offline installer |
| Install from a local area network (for enterprise apps) | - ClickOnce | Either web installer (see ClickOnce for restrictions) or offline installer |
Redistributable packages
The .NET Framework is available in two redistributable packages: web installer (bootstrapper) and offline installer (stand-alone redistributable). All .NET Framework downloads are hosted on the Download .NET Framework page. The following table compares the two packages:
| Web installer | Offline installer | |
|---|---|---|
| Internet connection required? | Yes | No |
| Size of download | Smaller (includes installer for target platform only)* | Larger* |
| Language packs | Included** | Must be installed separately, unless you use the package that targets all operating systems |
| Deployment method | Supports all methods: - ClickOnce - InstallAware - InstallShield - Windows Installer XML (WiX) - Manual installation - Custom setup (chaining) | Supports all methods: - ClickOnce - InstallAware - InstallShield - Windows Installer XML (WiX) - Manual installation - Custom setup (chaining) |
* The offline installer is larger because it contains the components for all the target platforms. When you finish running setup, the Windows operating system caches only the installer that was used. If the offline installer is deleted after the installation, the disk space used is the same as that used by the web installer. If the tool you use (for example, InstallAware or InstallShield) to create your app's setup program provides a setup file folder that is removed after installation, the offline installer can be automatically deleted by placing it into the setup folder.
** If you're using the web installer with custom setup, you can use default language settings based on the user's Multilingual User Interface (MUI) setting, or specify another language pack by using the /LCID option on the command line. See the section Chaining by Using the Default .NET Framework UI for examples.
Deployment methods
Four deployment methods are available:
You can set a dependency on the .NET Framework. You can specify the .NET Framework as a prerequisite in your app's installation, using one of these methods:
Use ClickOnce deployment (available with Visual Studio)
Create an InstallAware project (free edition available for Visual Studio users)
Create an InstallShield project (available with Visual Studio)
Use the Windows Installer XML (WiX) toolset
You can ask your users to install the .NET Framework manually.
You can chain (include) the .NET Framework setup process in your app's setup, and decide how you want to handle the .NET Framework installation experience:
Use the default UI. Let the .NET Framework installer provide the installation experience.
Customize the UI to present a unified installation experience and to monitor the .NET Framework installation progress.
These deployment methods are discussed in detail in the following sections.
Setting a dependency on the .NET Framework
If you use ClickOnce, InstallAware, InstallShield, or WiX to deploy your app, you can add a dependency on the .NET Framework so it can be installed as part of your app.
ClickOnce deployment
ClickOnce deployment is available for projects that are created with Visual Basic and Visual C#, but it is not available for Visual C++.
In Visual Studio, to choose ClickOnce deployment and add a dependency on the .NET Framework:
Open the app project you want to publish.
In Solution Explorer, open the shortcut menu for your project, and then choose Properties.
Choose the Publish pane.
Choose the Prerequisites button.
In the Prerequisites dialog box, make sure that the Create setup program to install prerequisite components check box is selected.
In the prerequisites list, locate and select the version of the .NET Framework that you've used to build your project.
Choose an option to specify the source location for the prerequisites, and then choose OK.
If you supply a URL for the .NET Framework download location, you can specify either the .NET Framework download page or a site of your own. If you are placing the redistributable package on your own server, it must be the offline installer and not the web installer. You can only link to the web installer on the .NET Framework download page. The URL can also specify a disc on which your own app is being distributed.
In the Property Pages dialog box, choose OK.
InstallAware deployment
InstallAware builds Windows app (APPX), Windows Installer (MSI), Native Code (EXE), and App-V (Application Virtualization) packages from a single source. Easily include any version of the .NET Framework in your setup, optionally customizing the installation by editing the default scripts. For example, InstallAware pre-installs certificates on Windows 7, without which .NET Framework 4.7 setup fails. For more information on InstallAware, see the InstallAware for Windows Installer website.
InstallShield deployment
InstallShield builds Windows app packages (MSIX, APPX), Windows Installer packages (MSI), and Native Code (EXE) installers. InstallShield also provides Visual Studio integration. For more information, see the InstallShield website.
Windows Installer XML (WiX) deployment
The Windows Installer XML (WiX) toolset builds Windows installation packages from XML source code. WiX supports a command-line environment that can be integrated into your build processes to build MSI and MSM setup packages. By using WiX, you can specify the .NET Framework as a prerequisite, or create a chainer to fully control the .NET Framework deployment experience. For more information about WiX, see the Windows Installer XML (WiX) toolset website.
Dotnetfx45 Full X86 X64 Exe
Installing the .NET Framework manually
In some situations, it might be impractical to automatically install the .NET Framework with your app. In that case, you can have users install the .NET Framework themselves. The redistributable package is available in two packages. In your setup process, provide instructions for how users should locate and install the .NET Framework.
Chaining the .NET Framework installation to your app's setup
If you're creating a custom setup program for your app, you can chain (include) the .NET Framework setup process in your app's setup process. Chaining provides two UI options for the .NET Framework installation:
Use the default UI provided by the .NET Framework installer.
Create a custom UI for the .NET Framework installation for consistency with your app's setup program.
Both methods allow you to use either the web installer or the offline installer. Each package has its advantages:
If you use the web installer, the .NET Framework setup process will decide which installation package is required, and download and install only that package from the web.
If you use the offline installer, you can include the complete set of .NET Framework installation packages with your redistribution media so that your users don't have to download any additional files from the web during setup.
Chaining by using the default .NET Framework UI
To silently chain the .NET Framework installation process and let the .NET Framework installer provide the UI, add the following command to your setup program:
<.NET Framework redistributable> /q /norestart /ChainingPackage <PackageName>
For example, if your executable program is Contoso.exe and you want to silently install the .NET Framework 4.5 offline redistributable package, use the command: Convert serial number to imei.
dotNetFx45_Full_x86_x64.exe /q /norestart /ChainingPackage Contoso
You can use additional command-line options to customize the installation. For example:
To provide a way for users to close running .NET Framework apps to minimize system restarts, set passive mode and use the
/showrmuioption as follows:dotNetFx45_Full_x86_x64.exe /norestart /passive /showrmui /ChainingPackage ContosoThis command allows Restart Manager to display a message box that gives users the opportunity to close .NET Framework apps before installing the .NET Framework.
If you're using the web installer, you can use the
/LCIDoption to specify a language pack. For example, to chain the .NET Framework 4.5 web installer to your Contoso setup program and install the Japanese language pack, add the following command to your app's setup process:dotNetFx45_Full_setup.exe /q /norestart /ChainingPackage Contoso /LCID 1041If you omit the
/LCIDoption, setup will install the language pack that matches the user's MUI setting.Note
Different language packs may have different release dates. If the language pack you specify is not available at the download center, setup will install the .NET Framework without the language pack. If the .NET Framework is already installed on the user’s computer, the setup will install only the language pack.
For a complete list of options, see the Command-Line Options section.
For common return codes, see the Return Codes section.
Chaining by Using a Custom UI
If you have a custom setup package, you may want to silently launch and track the .NET Framework setup while showing your own view of the setup progress. If this is the case, make sure that your code covers the following:
Check for .NET Framework hardware and software requirements.
Detect whether the correct version of the .NET Framework is already installed on the user’s computer.
Important
In determining whether the correct version of the .NET Framework is already installed, you should check whether your target version or a later version is installed, not whether your target version is installed. In other words, you should evaluate whether the release key you retrieve from the registry is greater than or equal to the release key of your target version, not whether it equals the release key of your target version.
Detect whether the language packs are already installed on the user’s computer.
If you want to control the deployment, silently launch and track the .NET Framework setup process (see How to: Get Progress from the .NET Framework 4.5 Installer).
If you’re deploying the offline installer, chain the language packs separately.
Customize deployment by using command-line options. For example, if you’re chaining the .NET Framework web installer, but you want to override the default language pack, use the
/LCIDoption, as described in the previous section.Troubleshoot.
Detecting the .NET Framework
The .NET Framework installer writes registry keys when installation is successful. You can test whether .NET Framework 4.5 or later is installed by checking the HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv4Full folder in the registry for a DWORD value named Release. (Note that 'NET Framework Setup' doesn't begin with a period.) The existence of this key indicates that .NET Framework 4.5 or a later version has been installed on that computer. The value of Release indicates which version of the .NET Framework is installed.
Important
You should check for a value greater than or equal to the release keyword value when attempting to detect whether a specific version is present.
Important
The following table lists the keys of released versions of the .NET Framework only. It doesn't list the keys of preview or pre-release versions.
| Version | Value of the Release DWORD |
|---|---|
| .NET Framework 4.8 installed on Windows 10 May 2019 Update | 528040 |
| .NET Framework 4.8 installed on all OS versions other than Windows 10 May 2019 Update | 528049 |
| .NET Framework 4.7.2 installed on Windows 10 April 2018 Update and on Windows Server, version 1803 | 461808 |
| .NET Framework 4.7.2 installed on all OS versions other than Windows 10 April 2018 Update, and Windows Server, version 1803. This includes Windows 10 October 2018 Update. | 461814 |
| .NET Framework 4.7.1 installed on Windows 10 Fall Creators Update and on Windows Server, version 1709 | 461308 |
| .NET Framework 4.7.1 installed on all OS versions other than Windows 10 Fall Creators Update and Windows Server, version 1709 | 461310 |
| .NET Framework 4.7 installed on Windows 10 Creators Update | 460798 |
| .NET Framework 4.7 installed on all OS versions other than Windows 10 Creators Update | 460805 |
| .NET Framework 4.6.2 installed on Windows 10 Anniversary Edition and on Windows Server 2016 | 394802 |
| .NET Framework 4.6.2 installed on all OS versions other than Windows 10 Anniversary Edition and Windows Server 2016 | 394806 |
| .NET Framework 4.6.1 installed on Windows 10 November Update | 394254 |
| .NET Framework 4.6.1 installed on all OS versions other than Windows 10 November Update | 394271 |
| .NET Framework 4.6 installed on Windows 10 | 393295 |
| .NET Framework 4.6 installed on all OS versions other than Windows 10 | 393297 |
| .NET Framework 4.5.2 | 379893 |
| .NET Framework 4.5.1 installed with Windows 8.1 or Windows Server 2012 R2 | 378675 |
| .NET Framework 4.5.1 installed on Windows 8, Windows 7 | 378758 |
| .NET Framework 4.5 | 378389 |
Detecting the language packs
You can test whether a specific language pack is installed by checking the HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv4FullLCID folder in the registry for a DWORD value named Release. (Note that 'NET Framework Setup' doesn't begin with a period.) LCID specifies a locale identifier; see supported languages for a list of these.
For example, to detect whether the full Japanese language pack (LCID=1041) is installed, retrieve the following named value from the registry:
| Key | HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv4Full1041 |
| Name | Release |
| Type | DWORD |
To determine whether the final release version of a language pack is installed for a particular version of the .NET Framework from 4.5 through 4.7.2, check the value of the RELEASE key DWORD value described in the previous section, Detecting the .NET Framework.
Chaining the language packs to your app setup
The .NET Framework provides a set of stand-alone language pack executable files that contain localized resources for specific cultures. The language packs are available from the Download .NET Framework pages:
Important
The language packs don't contain the .NET Framework components that are required to run an app; you must install the .NET Framework by using the web or offline installer before you install a language pack.
Starting with .NET Framework 4.5.1, the package names take the form NDP<version>-KB<number>-x86-x64-AllOS-<culture>.exe, where version is the version number of the .NET Framework, number is a Microsoft Knowledge Base article number, and culture specifies a country/region. An example of one of these packages is NDP452-KB2901907-x86-x64-AllOS-JPN.exe. Package names are listed in the Redistributable Packages section earlier in this article.
To install a language pack with the .NET Framework offline installer, you must chain it to your app's setup. For example, to deploy .NET Framework 4.5.1 offline installer with the Japanese language pack, use the following command:
NDP451-KB2858728-x86-x64-AllOS-JPN.exe /q /norestart /ChainingPackage <ProductName>
Download Dotnetfx45_full_x86_x64.exe Offline Installer
You do not have to chain the language packs if you use the web installer; setup will install the language pack that matches the user's MUI setting. If you want to install a different language, you can use the /LCID option to specify a language pack.
For a complete list of command-line options, see the Command-Line Options section.
Troubleshooting
Return codes
The following table lists the most common return codes for the .NET Framework redistributable installer. The return codes are the same for all versions of the installer. For links to detailed information, see the next section.
| Return code | Description |
|---|---|
| 0 | Installation completed successfully. |
| 1602 | The user canceled installation. |
| 1603 | A fatal error occurred during installation. |
| 1641 | A restart is required to complete the installation. This message indicates success. |
| 3010 | A restart is required to complete the installation. This message indicates success. |
| 5100 | The user's computer does not meet system requirements. |
Download error codes
See the following content:
Other error codes
See the following content:
Uninstalling the .NET Framework
Starting with Windows 8, you can uninstall .NET Framework 4.5 or later versions by using Turn Windows features on and off in Control Panel. In older versions of Windows, you can uninstall .NET Framework 4.5 or later versions by using Add or Remove Programs in Control Panel.
Important
For Windows 7 and earlier operating systems, uninstalling .NET Framework 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, or 4.8 doesn't restore .NET Framework 4.5 files, and uninstalling .NET Framework 4.5 doesn't restore .NET Framework 4 files. If you want to go back to the older version, you must reinstall it and any updates to it.
Appendix
Command-line options
The following table lists options that you can include when you chain the .NET Framework 4.5 redistributable to your app's setup.
| Option | Description |
|---|---|
| /CEIPConsent | Overwrites the default behavior and sends anonymous feedback to Microsoft to improve future deployment experiences. This option can be used only if the setup program prompts for consent and if the user grants permission to send anonymous feedback to Microsoft. |
/chainingpackagepackageName | Specifies the name of the executable that is doing the chaining. This information is sent to Microsoft as anonymous feedback to help improve future deployment experiences. If the package name includes spaces, use double quotation marks as delimiters; for example: /chainingpackage 'Lucerne Publishing'. For an example of a chaining package, see Getting Progress Information from an Installation Package. |
/LCIDLCIDwhere LCID specifies a locale identifier (see supported languages) | Installs the language pack specified by LCID and forces the displayed UI to be shown in that language, unless quiet mode is set.For the web installer, this option chain-installs the language package from the web. Note: Use this option only with the web installer. |
/logfilefolder | Specifies the location of the log file. The default is the temporary folder for the process, and the default file name is based on the package. If the file extension is .txt, a text log is produced. If you specify any other extension or no extension, an HTML log is created. |
| /msioptions | Specifies options to be passed for .msi and .msp items; for example: /msioptions 'PROPERTY1='Value'. |
| /norestart | Prevents the setup program from rebooting automatically. If you use this option, the chaining app has to capture the return code and handle rebooting (see Getting Progress Information from an Installation Package). |
| /passive | Sets passive mode. Displays the progress bar to indicate that installation is in progress, but does not display any prompts or error messages to the user. In this mode, when chained by a setup program, the chaining package must handle return codes. |
| /pipe | Creates a communication channel to enable a chaining package to get progress. |
| /promptrestart | Passive mode only, if the setup program requires a restart, it prompts the user. This option requires user interaction if a restart is required. |
| /q | Sets quiet mode. |
| /repair | Triggers the repair functionality. |
| /serialdownload | Forces the installation to happen only after the package has been downloaded. |
| /showfinalerror | Sets passive mode. Displays errors only if the installation is not successful. This option requires user interaction if the installation is not successful. |
| /showrmui | Used only with the /passive option. Displays a message box that prompts users to close .NET Framework apps that are currently running. This message box behaves the same in passive and non-passive mode. |
| /uninstall | Uninstalls the .NET Framework redistributable. |
Supported languages
The following table lists .NET Framework language packs that are available for .NET Framework 4.5 and later versions.
| LCID | Language – country/region | Culture |
|---|---|---|
| 1025 | Arabic - Saudi Arabia | ar |
| 1028 | Chinese – Traditional | zh-Hant |
| 1029 | Czech | cs |
| 1030 | Danish | da |
| 1031 | German – Germany | de |
| 1032 | Greek | el |
| 1035 | Finnish | fi |
| 1036 | French – France | fr |
| 1037 | Hebrew | he |
| 1038 | Hungarian | hu |
| 1040 | Italian – Italy | it |
| 1041 | Japanese | ja |
| 1042 | Korean | ko |
| 1043 | Dutch – Netherlands | nl |
| 1044 | Norwegian (Bokmål) | no |
| 1045 | Polish | pl |
| 1046 | Portuguese – Brazil | pt-BR |
| 1049 | Russian | ru |
| 1053 | Swedish | sv |
| 1055 | Turkish | tr |
| 2052 | Chinese – Simplified | zh-Hans |
| 2070 | Portuguese – Portugal | pt-PT |
| 3082 | Spanish - Spain (Modern Sort) | es |
See also
-->The .NET Framework 4.5 is a redistributable runtime. If you develop apps for this version of the .NET Framework, you can include (chain) .NET Framework 4.5 setup as a prerequisite part of your app's setup. To present a customized or unified setup experience, you may want to silently launch .NET Framework 4.5 setup and track its progress while showing your app's setup progress. To enable silent tracking, .NET Framework 4.5 setup (which can be watched) defines a protocol by using a memory-mapped I/O (MMIO) segment to communicate with your setup (the watcher or chainer). This protocol defines a way for a chainer to obtain progress information, get detailed results, respond to messages, and cancel the .NET Framework 4.5 setup.
Invocation. To call .NET Framework 4.5 setup and receive progress information from the MMIO section, your setup program must do the following:
Call the .NET Framework 4.5 redistributable program:
dotNetFx45_Full_x86_x64.exe /q /norestart /pipe section-nameWhere section name is any name you want to use to identify your app. .NET Framework setup reads and writes to the MMIO section asynchronously, so you might find it convenient to use events and messages during that time. In the example, the .NET Framework setup process is created by a constructor that both allocates the MMIO section (
TheSectionName) and defines an event (TheEventName):Please replace those names with names that are unique to your setup program.
Read from the MMIO section. In the .NET Framework 4.5, the download and installation operations are simultaneous: One part of the .NET Framework might be installing while another part is downloading. As a result, progress is sent back (that is, written) to the MMIO section as two numbers (
m_downloadSoFarandm_installSoFar) that increase from 0 to 255. When 255 is written and the .NET Framework exits, the installation is complete.
Exit codes. The following exit codes from the command to call the .NET Framework 4.5 redistributable program indicate whether setup has succeeded or failed:
0 - Setup completed successfully.
3010 – Setup completed successfully; a system restart is required.
1602 – Setup has been canceled.
All other codes - Setup encountered errors; examine the log files created in %temp% for details.
Canceling setup. You can cancel setup at any time by using the
Abortmethod to set them_downloadAbortandm_ installAbortflags in the MMIO section.
Chainer Sample
The Chainer sample silently launches and tracks .NET Framework 4.5 setup while showing progress. This sample is similar to the Chainer sample provided for the .NET Framework 4. However, in addition, it can avoid system restarts by processing the message box for closing .NET Framework 4 apps. For information about this message box, see Reducing System Restarts During .NET Framework 4.5 Installations. You can use this sample with the .NET Framework 4 installer; in that scenario, the message is simply not sent.
Warning
You must run the example as an administrator.
You can download the complete Visual Studio solution for the .NET Framework 4.5 Chainer Sample from the MSDN Samples Gallery.
The following sections describe the significant files in this sample: MMIOChainer.h, ChainingdotNet4.cpp, and IProgressObserver.h.
MMIOChainer.h
The MMIOChainer.h file (see complete code) contains the data structure definition and the base class from which the chainer class should be derived. The .NET Framework 4.5 extends the MMIO data structure to handle data that the .NET Framework 4.5 installer needs. The changes to the MMIO structure are backward-compatible, so a .NET Framework 4 chainer can work with .NET Framework 4.5 setup without requiring recompilation. However, this scenario does not support the feature for reducing system restarts.
A version field provides a means of identifying revisions to the structure and message format. The .NET Framework setup determines the version of the chainer interface by calling the
VirtualQueryfunction to determine the size of the file mapping. If the size is large enough to accommodate the version field, .NET Framework setup uses the specified value. If the file mapping is too small to contain a version field, which is the case with the .NET Framework 4, the setup process assumes version 0 (4). If the chainer does not support the version of the message that .NET Framework setup wants to send, .NET Framework setup assumes an ignore response.The MMIO data structure is defined as follows:
The
MmioDataStructuredata structure should not be used directly; use theMmioChainerclass instead to implement your chainer. Derive from theMmioChainerclass to chain the .NET Framework 4.5 redistributable.
IProgressObserver.h
The IProgressObserver.h file implements a progress observer (see complete code). This observer gets notified of download and installation progress (specified as an unsigned
char, 0-255, indicating 1%-100% complete). The observer is also notified when the chainee sends a message, and the observer should send a response.
ChainingdotNet4.5.cpp
The ChainingdotNet4.5.cpp file implements the
Serverclass, which derives from theMmioChainerclass and overrides the appropriate methods to display progress information. The MmioChainer creates a section with the specified section name and initializes the chainer with the specified event name. The event name is saved in the mapped data structure. You should make the section and event names unique. TheServerclass in the following code launches the specified setup program, monitors its progress, and returns an exit code.The installation is started in the Main method.
Before launching the installation, the chainer checks to see if the .NET Framework 4.5 is already installed by calling
IsNetFx4Present:You can change the path of the executable (Setup.exe in the example) in the
Launchmethod to point to its correct location, or customize the code to determine the location. TheMmioChainerbase class provides a blockingRun()method that the derived class calls.The
Sendmethod intercepts and processes the messages. In this version of the .NET Framework, the only supported message is the close application message.Progress data is an unsigned
charbetween 0 (0%) and 255 (100%).The HRESULT is passed to the
Finishedmethod.Important
The .NET Framework 4.5 redistributable typically writes many progress messages and a single message that indicates completion (on the chainer side). It also reads asynchronously, looking for
Abortrecords. If it receives anAbortrecord, it cancels the installation, and writes a finished record with E_ABORT as its data after the installation has been aborted and setup operations have been rolled back.
A typical server creates a random MMIO file name, creates the file (as shown in the previous code example, in Server::CreateSection), and launches the redistributable by using the CreateProcess method and passing the pipe name with the -pipe someFileSectionName option. The server should implement OnProgress, Send, and Finished methods with application UI-specific code.