Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

Tagging subscribers to this area: @dotnet/area-extensions-hosting
See info in area-owners.md if you want to be subscribed.

namespace Microsoft.Extensions.Hosting
{
    [Serializable]
    public sealed partial class HostAbortedException : Exception
    {
        public HostAbortedException() { }
        private HostAbortedException(System.Runtime.Serialization.SerializationInfo info, System.Runtime.Serialization.StreamingContext context) { }
        public HostAbortedException(string? message) { }
        public HostAbortedException(string? message, System.Exception? innerException) { }
    }
}

@maryamariyan Please give a review too 👍🏼

By the way, is it correct that build.cmd -vs Microsoft.Extensions.HostFactoryResolver does not work?
Or why is there no solution file for the project?

By the way, is it correct that build.cmd -vs Microsoft.Extensions.HostFactoryResolver does not work?
Or why is there no solution file for the project?

This library is "special" in that it doesn't actually produce a library in the traditional sense.

This is a nuget package that contains the .cs files. When consumers use this package, these files get included directly in the consumer's project. So no .dll gets created by this library.

That said, this folder still contains a test project, and the src still has a csproj file, even though it doesn't build a .dll. So I'm not sure why there isn't a .sln file. It may have just been an oversite.

@ViktorHofer - do you happen to know why there is no .sln file here?

@ViktorHofer - do you happen to know why there is no .sln file here?

Most probably an unintentional omission in d13863e, which added the library to dotnet/runtime. Feel free to add one.

@ViktorHofer - do you happen to know why there is no .sln file here?

Most probably an unintentional omission in d13863e, which added the library to dotnet/runtime. Feel free to add one.

Should I do that right along with this PR or would it be better to write an issue for it and do that in a follow up?

No need for an issue, that would be way too much overhead. Just add it to this PR. And don't bother with the version header at the top of the solution file as that will be overwritten anyways, whenever we batch update all solution files.

runtime (Libraries Test Run release mono Linux x64 Debug) failure is #13757
runtime (Build Browser wasm Linux Release LibraryTests) failure is #58643

This PR is, I believe, causing problems in dotnet/aspnetcore#41999. We use Microsoft.Extensions.HostFactoryResolver.Sources and it seems src/libraries/Microsoft.Extensions.HostFactoryResolver/src/HostFactoryResolver.cs ended up w/o the necessary reference to Microsoft.Extensions.Hosting in our scenarios. Do we need to react or should we expect a fix in the M.E.HFR.Sources package❔