One of em was not a rebuild. but oh well.
Couple tinges I. notice:
-> Target Echoes started.
D: Ignoring outdated cached data for ResolveReferences (11:09 PM ≥ 11:05 PM)
-> Task RemObjects.EBuild.Elements.ElementsProcessNuGetReferences started for ConsoleApplication5, Echoes.
D: Package Microsoft.NETCore.App found in local cache.
W: Package Microsoft.NETCore.App:2.1.0 has no deliverable for platform 'netcoreapp'.
I’ve improved the logging output here. This one will actually be diced by my new build; it happens because the implicit reference was not specific to a version, so it gets upgraded to the latest (2.2.0 here for me) which, indeed, does not have a deliverable for netcore2.1 (only 2.2).
The build I sent you last night already fixes this, as it pulls in
[2.1.0] exactly, which works.
Right now, this issue is ignored (just a warning); and somehow the compiler pulls in the regular mscorlib.dll from Mono (that’s a compiler bug I need to log for Carlo for next week), which is why the build still succeeds.
I’ve now improved logging to show the actual version numbers:
D: Package Microsoft.NETCore.App:2.2.0 found in local cache.
E: Package <NameAndVersion = Microsoft.NETCore.App:2.2.0> has no deliverable for platform 'netcoreapp 2.1'.
and I’ve also made this a failing error instead of a warning, so the build will now fail if a (direct) package reference has. no deliverable. (indirect references without deliverable will remain non-fatal warnings only).
After fixing this, adding Dapper back to the project still/again compiles for me.
Can you retry with the new built from last night? in a short while, I’ll also send you a new build with the additional fixes I made, mainly for the better/more precise logging.