David Ferretti

Are you talking about `dotnet pack`? The pack command will produce a nuget package, not the publish command. You should be able to `dotnet publish` a class library and get...

Here is an article from years ago explaining how unobserved Task exceptions can cause crashes: https://devblogs.microsoft.com/pfxteam/task-exception-handling-in-net-4-5/ And here is a more recent conversation about it (with a comment from the...

I've also seen similar issues where a developer might accidentally cause the process to crash by not realizing they were creating unobserved Task exceptions in writing essentially `async void` versions...

It's more just about the fact that it is hard or impossible to properly handle exceptions when you are calling an `async void` method. If you are _writing_ an `async...

Ah so this guidance is specific to ASP.NET CORE: > Use of async void in ASP.NET Core applications is ALWAYS bad. In ASP.NET Core there shouldn't ever be a place...

The guidance here to never just return the Task seems like a safer default to use. In that video it looks like he mentions the troubles you can have if...

I have read elsewhere in this repo that SharpYaml is an implementation detail and shouldn't be exposed in the public API if avoidable. The `Mark` struct that YamlNode.Start and End...

Sure - my use case is a C# Source Generator I am working on. I read in an openapi spec and generate models based on the schemas found in the...

And I should add, I am hoping to include line numbers instead of just `found at schema #/components/...` because Source Generators can include `Location` information with line numbers, and VS...

One tricky part I am not sure what to do about: how to handle documents that are dynamically created / added to. My first thought would be to attach some...