Opened PR 17999 to address.

PowerShell doesn't directly reference Microsoft.Extensions.ObjectPool. Instead, PowerShell references System.Private.ServiceModel, which depends on Microsoft.Extensions.ObjectPool (>= 5.0.10) even for its latest version (4.10.0).

The [cgmanifest.json](https://github.com/PowerShell/PowerShell/pull/17999/files#diff-2dbca354d25860d8a564159de6e6aa5be32423f7c475a9c120383d5df7c2d66a) file is auto-generated to reflect the dependencies of PowerShell, which is then used to auto-generate our ThirdPartyNotice. So, it shouldn't be changed.

In you case, you may want to read the "Resolving dependency conflict" doc. The samples in https://github.com/daxian-dbw/PowerShell-ALC-Samples may also be helpful to you.

GitHub

GitHub - daxian-dbw/PowerShell-ALC-Samples: Samples for solving PowerShell module assembly dependency conflicts using `AssemblyLoadContext`.

Samples for solving PowerShell module assembly dependency conflicts using `AssemblyLoadContext`. - GitHub - daxian-dbw/PowerShell-ALC-Samples: Samples for solving PowerShell module assembly depende...

This issue has been marked as declined and has not had any activity for 1 day. It has been closed for housekeeping purposes.

@daxian-dbw Microsoft.Extensions.ObjectPool is distributed in the aspnet.core shared runtime.

This has no impact for importing the PowerShell SDK into AspNet.Core. (dependencies are satisfied)
On the other hand, it can block the loading of AspNet.Core in PowerShell.

Wouldn't it be possible to put an explicit dependency in Microsoft.PowerShell.SDK?

I'm working on PowerShell WASM and need to be able to load AspNet.Core into PowerShell for easier development.
I put an ALC in my module but however it is possible to reopen the issue.

Suffering same problem. We cannot run PowerShell commandlets that use/reference aspnet.core

As a workaround we currently manually remove or replace Microsoft.Extensions.ObjectPool.dll in the PowerShell installation directory.

Also see issue dotnet/aspnetcore#47352

Would be great if this could be resolved.

same problem trigger on .net 8.0.1

遭受同样的问题。我们无法运行使用/引用 aspnet.core 的 PowerShell commandlet

作为解决方法，我们目前手动删除或替换 PowerShell 安装目录中的 Microsoft.Extensions.ObjectPool.dll。

另请参阅问题 dotnet/aspnetcore#47352

如果这个问题能得到解决，那就太好了。

Your method seems to work