Benefit of Self-Contained Deployment for IIS?

Question

Microsoft's documentation lists a benefit of doing a Self-Contained Deployment (SCD) is not having to install anything, including the .net core framework. But, I found out from other sources, that in order to actually use SCD on an IIS server, it is required to install the .net core hosting bundle...

I thought the point of self-contained deployment was that it was "self-contained". If I have to install something whether I'm doing a SCD, or doing Framework-Dependent deployment, then I would choose framework- dependent, because it is much smaller.

Is there a reason .net core hosting bundle needs to be installed on the IIS server? Can I find a way to not install it?

I have a feeling that the documentation is referring to deploying to unix/linux. Do you have a link to the documentation? — DFord
This is the documentation talking about deployment options, but i don't have the documentation where I learned that i needed the hosting bundle. That was more trial and error, and reading other articles. docs.microsoft.com/en-us/dotnet/core/deploying/index — RAZLFRAZ
SCD is almost useless if you deploy to Windows/IIS. The hosting bundle is always a must, as ASP.NET Core module can only be installed from it. — Lex Li
Alright, that's exactly what i wanted to know. Thanks. Just wanted to make sure i wasn't missing an obvious reasoning. — RAZLFRAZ

DFord DFord · Accepted Answer · 2019-02-01T16:20:16

The self contained deployments do not contain the native dependencies for running a .NET core application, see the first paragraph of this section.

You can follow the native dependencies of .NET core to a github project that has the native prerequisites for windows, macOS and linux. native prerequisites

Benefit of Self-Contained Deployment for IIS?

1 Answers