* Flesh out `ByteRangeStream` methods to make it always limit reads
- #206
- `Seek(...)` was a no-op, `Position` was incorrect if `_lowerbounds != 0`, `ReadAsync(...)` read entire inner `Stream`
- rewrite `ByteRangeStreamTest` to cover new `ByteRangeStream` members and hold fewer resources
- remove `DelegatingStream.CopyToAsync(...)` override because it copied entire inner `Stream` and was not needed
- base implementation invokes `ReadAsync(...)`
- no need to get things working where VS 2019 preview is the only build available
- start using .NET Core SDK 2.1.403
- confirmed AppVeyor and wsr-tc agents both have this SDK
- correct ordering issue with restore of System.Net.Http.Formatting.NetCore project
- match combination of eb1bfe51a1 and 986889d81c i.e. the upgrade to 5.2.5 / 3.2.5 Preview1
- also change README.md to use "Web API 5.x" instead of "Web API 2.x"
- revert part of eb1bfe51a1
- Web Pages assemblies do not get new versions release-to-release
- CI still builds Facebook assemblies with version 1.1.0.0 and that doesn't need to change
- in recent CI run, another test failed because `MediaTypeFormatter.MaxHttpCollectionKeys == 1` temporarily
- also left `MediaTypeFormatter.MaxHttpCollectionKeys == 125` which could affect later tests
- XML serializers handle `DBNull` on some machines but not others
- possible an underlying problem was fixed recently, in .NET Core SDK 2.0.3
- but, better to make builds work almost everywhere and wait for .NET Core SDK 2.1.x (where `DBNull` is seralizable)
- simplify .NET Standard projects and use Microsoft.NET.Sdk in test project
- depend on Newtonsoft.Json v10 and Newtonsoft.Json.Bson v1 packages
- Newtonsoft.Json v9.0.1 has a reduced API when targeting .NET Standard
- adjust a few tests to handle changes between v9 and v10
- test .NET Standard library on both .NET 4.6.1 and .NET Core 2.0
- update test/Directory.Build.targets to handle testing with .NET Core; use it from Runtime.msbuild
- adjust a few tests to handle .NET Core 2.0 differences and gaps
- found and fixed a broken test in `HttpValueCollectionTest`
- some properties with defaults based on `$(IsTestProject)` were set incorrectly
- Microsoft.TestCommon project is not really a test project
- follow-up to 4b309584ad
- part of #65
Few manual changes:
- temporarily remove xUnit analyzers from System.Web.Razor.Test
- work around xunit/xunit#1502
- should restore analyzers as part of a #96 fix
- use `Assert.IsAssignableFrom<T>(...)`, `Assert.IsType<T>(...)` and `Assert.Single(...)` return values
- avoid xUnit1013, Public method should be marked as test
- mark a helper method `internal`
- fix xUnit1026, `[Theory]` method doesn't use all parameters
- add new data set properties
- suppress xUnit2013, Do not use equality check to check for collection size.
- calls `Count` because the `Mock<T>` does not set up `GetEnumerable()`
- `Assert.Equal<T>(...)` -> `Assert.Equal(...)`
- avoid Linq's `.Where` inside `Assert.Contains(...)` and similar
- enable app domains in all testing; `denied` now breaks testing in VS
- VS runner previously ignored this setting; see xunit/xunit#1533
- remove `"shadowCopy": false` setting too
- with updated xUnit packages, this setting slows testing down significantly
Doug Bunting
Doug Bunting
AlexLEWIS
Hans van Bakel
Tornike Kharaishvili
Maxime Rouiller
Trofimov Ivan Andreevich
Max Horstmann
JamesSinclairBiomni
Daniel Roth
Brandon Dahler
Patric Forsgard