Revised ASP.NET Core module installer for Windows ARM64

[lextm]

Revised ASP.NET Core module installer for Windows ARM64

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

• Switch to LoadLibraryEx with LOAD_LIBRARY_SEARCH_DLL_LOAD_DIR flag set, so that the pure forwarder works as desired.
• Add ARM64X pure forwarders.
• Revise WiX installer to utilize ARM64X pure forwarders

Fixes #47115.

Description

About the change in HandlerResolver.cpp

To implement all proposed installer changes in #47115, then in the out-of-process folder three files present,

1. aspnetcorev2_outofprocess.dll, an ARM64X pure forwarder.
2. aspnetcorev2_outofprocess_arm64.dll, the pure ARM64 handler.
3. aspnetcorev2_outofprocess_x64.dll, the x64 handler.

Before this change, LoadLibrary only loads the pure forwarder, but then scans the default folders (the dll folder is not included) to load the actual handler which obviously fails.

After this change, LoadLibraryEx can pick up the correct handler as the dll folder is added in the search folder list.

About files in Forwarders folder

Source code for the two ARM64X pure forwarders.

About changes in ANCMV2 folder

Before this change, only ARM64 web apps can run on IIS.

After this change, the new file structure enables ARM64/x64/x86 side by side execution on IIS.

[ghost]

Thanks for your PR, @lextm. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[lextm]

For some unknown reason, this section has to be commented out if compiling on Windows 11 ARM64.

[wtgodbe]

Looks like we're hitting some errors in the new Forwarder project, are you seeing these locally?

The system cannot find the path specified.
'cl' is not recognized as an internal or external command,
operable program or batch file.
The system cannot find the path specified.
'cl' is not recognized as an internal or external command,
operable program or batch file.
The system cannot find the path specified.
A subdirectory or file D:\a_work\1\s\artifacts\obj\AspNetCoreModuleForwarders already exists.

[lextm]

I don't see the errors locally, but expected something like this. I will dig into the CI log files and see what further changes are needed.

[lextm]

I was able to reproduce the cl errors by running .\eng\build.cmd -ci xxxx as it seems to set up the build environment differently from build.ps1 under src\Installers\Windows.

However, after applying the changes CI still failed and this time I am not familiar with the errors.

[wtgodbe]

However, after applying the changes CI still failed and this time I am not familiar with the errors.

That looks like a transient error, I hit rerun.

To be transparent, we're still trying to figure out if we want to take this change. We think the number of customers who use ANCM/IIS on win-arm64 is relatively low, and we may not have the resources on our team to provide support for this new scenario. If you could share some info on how strong your need is for this feature, that would help us come to a decision.

[mkArtakMSFT]

Closing as we don't plan to take this change at this time.