Paulo Morgado

For fire and forget, I'd choose any option on [this page](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/host/hosted-services "Background tasks with hosted services in ASP.NET Core") over `Task.Run`.

The hosting environment can make some guarantees about work it's managing. It can make nothing about `Task.Run`. Or can it?

The transformations are applied, but the transformed files are removed from the list of files to copy in the `CopyAllFilesToSingleFolderForPackage` target from Microsoft.Web.Publishing.targets. ```xml ``` Changing the order of targets...

I was able to work around it adding these items: ```XML ```

Maybe it's overkill but, probably, a specific SDK would circumvent the need for having any kind of project that Visual Studio needs to understand.

I don't have any problematic use case. I just don't think it's a good practice to throw everything and the kitchen think in an assembly just because it might be...

@austinlparker, in other words, not in production scenarios.

It's more a case of separation of concerns at this moment than being technically problematic. And I'm not talking about multiple assemblies in the same package but multiple packages.

I find it strange that I can set the operation name on a span whenever I want to, but cannot read it. The same for tags, by the way. If...

Done! #448