Andrew Teece

Many years ago when I was a young programmer I searched for 2 days for a un-reproducible bug around this. It was because my end-user had copied something via email...

@hacker1db This is my intended use of the tool too for efficiency. My plan was to use the ".NET Core Global Tool Installer" task to ensure it is installed on...

I'll try to throw something together next week. I faced/found the issue when using Flurl in a MSTest v2 project. I hooked into the AfterCallAsync (also tried AfterCall) in order...

So initially i've been unable to replicate using a .net Core Console App. Further reading on the subject suggests that if SynchronizationContext.Current is null then ConfigureAwait(false) will actually do nothing/isn't...

Forgot to mention this is also commented in the community, but without a supported/upgrade-safe solution which is why i have logged teh bug. https://community.mailcow.email/d/2983-helo-command-rejected

My understanding is that you don't have to reference the framework, you can refernce the individual NuGet packages for the components you need. By not demanding the framework and instead...

The change I'm suggesting isn't to re-create a server nuget; although that may be a good idea. My suggestion is that be referencing the required NuGet packages directly instead of...

Gotcha. I understand what you mean now. And as there is no Microsoft.AspNetCore.App package you can't reference them another way. I do still think this is an issue - I...

Maybe the team responsible for the core Sdk should be moving the SignalR functionality into the core Sdk rather than the AspNetCore one?

> If you don't want to install the ASP.NET Core runtime on your host machine, then publish your app as self-contained. https://learn.microsoft.com/dotnet/core/deploying/#publish-self-contained I did look into this but it isn't...