Improve edit-run cycle time on .Net Core

129 Views Asked by At

I'm trying to improve the performance in Logary and am bumping into an unexpected issue with .Net Core; even a single-character change in Logary.PerfTests

enter image description here

causes a complete restore throughout all of the repository (I think), with this as a result:

Paket eating my CPU

Can I somehow improve the change-run performance? I've tried the core-only sln file, but dotnet core/rider seems to restore all nugets for all projects no matter.

Here's paket.dependencies for the group:

group Benchmarks
    source https://api.nuget.org/v3/index.json
    framework net471, netcoreapp2.0
    redirects on
    nuget FParsec
    nuget FSharp.Core
    nuget Hopac
    nuget NodaTime
    nuget Expecto
    nuget Expecto.BenchmarkDotNet

Here's the PR/code in full https://github.com/logary/logary/pull/323

0

There are 0 best solutions below