9 Commits

Author SHA1 Message Date
Toni Solarin-Sodara a1d47d3775 Update documentation (#1018) 2020-12-16 15:09:46 +01:00
Marco Rossignoli 62ff6d7c2c Update CONTRIBUTING.md (#793)
Update repo build workflow.
2020-04-05 18:04:07 +02:00
Marco Rossignoli caac526075 Move/Pin to 3.1 runtime (#688)
Move/Pin to 3.1 runtime
2020-01-14 14:46:22 +01:00
Marco Rossignoli 53562c6460 Add integration test for all drivers mbuild/vstest/.net tool (#639)
Add integration test for all drivers mbuild/vstest/.net tool
2019-12-06 16:43:24 +01:00
Philipp 872e087e6a Fix missing quotation mark for test command (#505) 2019-08-12 14:06:12 +02:00
Andrew Arnott 497c6c534d Remove redundant section 2019-05-29 10:28:46 -06:00
Andrew Arnott b46cab34f5 Add sample test parameters
Co-Authored-By: Marco Rossignoli <marco.rossignoli@gmail.com>
2019-05-29 07:24:33 -06:00
Andrew Arnott 664eb7303a Remove build.proj in favor of regular dotnet commands
Simple removal of the build.proj file allows `dotnet` commands to just work without having to specify the sln file explicitly, which is really nice.

The build.proj was building all projects 3 times (build, test, and pack all rebuilt everything and repeated package restore, etc.), so it was slower than necessary anyway.

In its place:
1. folks can just use `dotnet build` or whatever command suits them.
1. Azure Pipelines simply executes dotnet commands, which I break up into 4 steps so the pipeline can show timings for each step, etc.

Because we use the Azure Pipelines DotNetCoreCLI task for running tests, the test results are automatically collected and reported as a searchable database.
Test results can be analyzed over time to see how they perform, which ones are unstable, etc.
2019-05-29 00:35:41 -06:00
Oluwatoni Solarin-Sodara 5c1ea92d7c add separate contribution guide document 2019-01-17 11:36:16 +01:00