Caleb Frederickson

Looks like the `Exception of type 'System.Exception' was thrown.` exception is still occurring when an attempt is made to run rules defined in an assembly when `-IncludeDefaultRules` is `false`, presumably...

This would be particularly useful for registrations of `HttpClient`. Currently to have differently configured `HttpClient` instances one must use a factory for each consumer of `HttpClient`. The problem here is...

https://gist.github.com/Stroniax/c6ffd55b9506d4bfb7feb4036bc895b5 The `HttpClient` is created in the factory method, and therefore the container will not dispose of it. With this suggestion, I would be able to use something more like...

I agree with using PSKubectl's implementation of `AsyncCmdlet`. As mentioned years ago, more and more libraries are becoming async-only. I'm frequently writing cmdlets that have to deal with these libraries....

> Perhaps PowerShell 8 will be the async aware one, which uses a special compatibility mode to run PowerShell 5 and PowerShell 7 modules. Async APIs usually have no problem...

> ```powershell > Update-TypeData -TypeName 'Deserialized.System.DateTimeOffset' -TargetTypeForDeserialization 'System.DateTimeOffset' > ``` > > ### Then register the TypeConverter for that TargetType: > ```powershell > Update-TypeData -TypeName 'System.DateTimeOffset' -TypeConverter 'DateTimeOffsetDeserializer' > ```...

I am also currently experiencing this problem. `dotnet --version` returns `9.0.100-rc.1.24452.12`. Unsure if this is related to https://github.com/dotnet/aspnetcore/issues/26072.

I have noticed that it seems to be when I hit the first async boundary that releases context. So logging works until I hit an `await` that is not completed....