Alexander Batishchev
Alexander Batishchev
@MaxLevs ping.
Unfortunately EF.Extended isn't testable at all and author isn't going to address that.
Looks good to me. However, I'd stick with CRUD naming, i.e. Update(...). Delete can have no overload so would be used on top of Where(...). Delete(predicate) would be a nice...
+@avparuch who might be interested in perf improvements in https.sys
Same here, two years later. Any change to get it fixed? Any known workarounds? I have a multi-target library and 2 sets of tests: .NET 4.6.2 and .NET Core 2.0.
The fact this know bug is open for 2+ years and kept without movement is quite frustrating.
>But your unit test project MUST target a framework. Nothing can run as ".NET Standard". Hmm, no. It's not how it works. Test project produces merely a DLL. VSTest.Console.exe is...
Any updated on this, please? I drags on, and on, and on. >Warning NU1701: Package 'MSTest.TestAdapter 2.1.2' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project...