Figure out Buildalyzer's Overeager Clean

[Noggog]

Right now we're using Buildalyzer to get some metadata about solutions/projects. Comes with the downside of cleaning for no reason. Either need to ditch it, or find the option to turn that off, as it's wasting time redoing work

Related issue: phmonte/Buildalyzer#105

[Noggog]

tstavrianos' suggestion:
https://gist.github.com/tstavrianos/7dd5e6e2ca8236bbef27ac742d8f089f

[tstavrianos]

After some time looking into this, I think it might be easier to avoid buildalyzer & roslyn (until microsoft's toolset is more easily usable from inside c#).
If you need to know the projects output directory, you can force it to be whatever you want instead (such as temp?):
dotnet build <project/solution> --output <path>

If you don't need the output, you can use:
dotnet run --project <projectfile>

Both of these will avoid the endless dependencies that roslyn/msbuild have to work correctly.

[Noggog]

Oh, nice. I didn't even think about dotnet run! That might be the cleanest route by far

[Noggog]

68208d0

Worked like a charm. Lots of wiring removed related to finding the path to the exe to run. As a side effect, Buildalyzer's functionality that cleans is no longer needed. Synthesis' time-to-run is now near instant after starting up, as before it had to locate all the exes to run, and then rebuild everything because they had been cleaned. Now it just starts up and is ready to go.

Glorious!