dotnet / dotnet/aspnetcore

Make AspNetCoreModuleV2 distributable locally with the application rather than installable globally

Open
#39,099 5 comments 0 reactions 0 assignees View on GitHub
area-networking feature-iis investigate
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 6h
Merged PRs (30d)
290

Description

### Is your feature request related to a problem? Please describe.
On IIS farms, hosting bundle must be installed separately on multiple servers just to have the AspNetCoreModuleV2 available. The Core runtime doesn't have to be installed as it can be deployed together with the app. But the requirement to actually have the module installed makes the deployment more difficult that it could be.

Found only [this thread on SO](https://stackoverflow.com/questions/63339145/installing-aspnetcoremodulev2-by-itself-or-making-sure-it-gets-installed) but the proposed solution still requires an extra package to be installed.

### Describe the solution you'd like
An ideal solution would be to have the module packed together within the application. In this ideal solution, I could publish an app to get a DLL of the app, dozens of DLLs of the current runtime and one AspNetCoreModuleV2 DLL. The web.config would refer to this module rather than to a module that has to be installed globally.

If there's an official way to do this currently but I just miss it, I would be glad to get a reference to an existing solution. Regards.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.