Quentin

@tmendez3 Whether or not increasing your thread pool minimum will help depends on your system. I use AsyncLock mainly as part of a cache-aside implementation to keep multiple consumers from...

@milspiir Not that I've seen, and I'm still on v3. I did remove any and all mixed sync/async locking on any AsyncLock objects and that made no difference in the...

Sure, that works. I might suggest that any constructors that are available publicly for netfx should also be publicly available for corefx, baring any missing functionality, but I don't have...

Probably don't need to worry much about people targeting core v1.0-2.0, and I agree the `connectionStringName` constructor is unnecessary. You could possibly target netcoreapp1.0, 1.1, and 2.0 and use those...

That also looks like it could work.. One thing I should mention is that I'm also trying to use Microsoft.Data.SqlClient over System.Data.SqlClient - the relevant area in AsyncPoco is `DatabaseType.Resolve`...

No rush, I have a reflection-based work-around for now, and it will probably be several weeks still before I'm fully through the rest of work to retarget for .Net Core.

> > Could not load type 'Microsoft.AspNetCore.Mvc.Internal.IHttpRequestStreamReaderFactory' from assembly 'Microsoft.AspNetCore.Mvc.Core, Version=2.2.5.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. > > Been using your project for a couple of personal ASP.NET Core projects, thought I would...

> Is there a reason you would want to pin an older runtime version? I notice that Imageflow.Server references Imageflow.AllPlatforms but I am wondering if we can utilize Imageflow.NativeRuntime.win-x86_64-haswell or...