Pablo Carbonell

I think I found a workaround using [AsyncLocal](https://docs.microsoft.com/en-us/dotnet/api/system.threading.asynclocal-1?view=netframework-4.8).

Understood. In my case I am using ASP.NET Core and because of that I was able work around this using AsyncLocal. This lets you create static variables that have different...

Below is a wrapper that instantiates a different `IFileManager` on each async flow. To use it, we simply call `GlobalFileManager.LocalManager = myInstance` ```csharp using LibSassHost; using System.Threading; namespace Integrative.ModelerEngine.Styles {...

Hello @karelz , your recommendation is not to use HttpClient and use Kestrel that has been moved into ASP.NET Core. However, I don't fully understand how to go from one...

Would it make sense for the DotNetCore team to offer the HttpClient class as a thin wrapper that under the hood uses Kestrel? This would help with migration A LOT.

@jkotas thank you for the links. I checked out the documentation and the references needed are specific to NET Core. Ideally we should have HttpClient or its replacement compiling under...

Hello @davidfowl ! If I understood correctly then option 2 is what HttpListener is for. Right now, if you have HttpListener, the Portability Analysis tool tells you that you're good...

> The entire discussion is about supporting the existing API, not about a replacement right? I personally would be open to change my code as long as we get to...

Will do once the repo reaches 100 starts

This blog below is a really good starting point. I got everything to work and now I'm deciding between Ooui and Razor (just ignore the React part, it's optional and...