OwnageIsMagic

https://blog.stephencleary.com/2013/04/implicit-async-context-asynclocal.html >Similar code will compile targeting .NET 4.0 (with Microsoft.Bcl.Async); however, it will not work correctly (unless it happens to run on .NET 4.5) because the logical call context is...

Looks like System.ValueTuple conflicts with itself if I only have Theraot.Core (which have System.ValueTuple 4.3.0) it compiles cleanly In another project where I have Vanara.Core, which have dependency on both...

[Repro.zip](https://github.com/theraot/Theraot/files/8145365/Repro.zip) Here is reproduction To compile remove one of dependencies in `ClassLibrary1`

even nastier it can't build anything that have transitive dependency on Vanara.Core  ClassLibrary succeeds, ConsoleApp fails.

Probably you just need to update System.ValueTuple 4.3.0 to 4.5.0 in Theraot.Core to resolve this

And if I set `true` it can't even build ClassLibrary.

"System.ValueTuple, Version=4.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" is assembly for netstandart (strange version number and it has the same PublicKeyToken) See [4.3.0](https://www.nuget.org/packages/System.ValueTuple/4.3.0) vs [4.5.0](https://www.nuget.org/packages/System.ValueTuple/4.3.0) (Framework tab) I think this is somehow related to...

@NN--- now I have 2 libs with ValueTuple 4.3.0 and 5 with 4.5.0 in my dependency graph nice job xD

> Simply add System.ValueTuple 4.5.0 package reference to your project. this doesn't work

Fixed by #233 ?