- 12 Mar, 2019 1 commit
-
-
Jan Tattermusch authored
-
- 06 Feb, 2018 1 commit
-
-
ObsidianMinor authored
Updated NUnit packages, removed NUnitLite added packages for dotnet and Visual Studio, changed dotnet command in buildall to dotnet test, and deleted Program.cs (because it's no longer required).
-
- 24 May, 2017 1 commit
-
-
Jon Skeet authored
This has one important packaging change: the netstandard version now depends (implicitly) on netstandard1.6.1 rather than on individual packages. This is the preferred style of dependency, and shouldn't affect any users - see http://stackoverflow.com/questions/42946951 for details. The tests are still NUnit, but NUnit doesn't support "dotnet test" yet; the test project is now an executable using NUnitLite. (When NUnit supports dotnet test, we can adapt to it.) Note that the project will now only work in Visual Studio 2017 (and Visual Studio Code, and from the command line with the .NET Core 1.0.0 SDK); Visual Studio 2015 does *not* support this project file format.
-
- 14 Jul, 2016 2 commits
- 02 Aug, 2015 1 commit
-
-
Jan Tattermusch authored
-
- 17 Jul, 2015 2 commits
-
-
Jan Tattermusch authored
-
Jon Skeet authored
We'll see what I've missed when CI fails...
-
- 26 Jun, 2015 1 commit
-
-
Jon Skeet authored
ProtoDump isn't currently useful, but will be when ToString emits JSON: fixed. ProtoBench: deleted; we should reinstate when there's a common proto3 benchmark. ProtoMunge: delete; not useful enough to merit fixing up. Removed the [TestFixture] from ByteStringTest as Travis uses a recent enough version of NUnit.
-
- 25 Jun, 2015 1 commit
-
-
Jon Skeet authored
The solution as a whole doesn't build yet - we probably want to remove ProtoDump and ProtoMunge entirely, and ProtoBench should use Jan's new benchmarks for parity with Java. The version of NUnit on my machine, packaged with Mono 3.12.1, is only NUnit 2.4.2, which is extremely old - it still requires an explicit [TestFixture] attribute on test fixtures. I've added one just for ByteStringTest for the moment so that we can see some tests passing in Travis, but as part of a separate PR we should work on making sure we're using a recent NUnit version. (It may already be doing so, but we can check that once it's working and merged.)
-
- 13 May, 2015 1 commit
-
-
Jan Tattermusch authored
-