Sometimes, our readers send us a story. Sometimes they send us some bad code. Sometimes, they just need a place to vent their frustrations. Paul T had some frustrations. Paul's team is migrating from .Net to .NetCore, and as one might imagine, that creates a lot of build failures.

Their Team City build environment sometimes doesn't give the most helpful messages:

[15:50:31][Step 1/9] publish (3s) [15:50:31][publish] Starting: "c:\Program Files\dotnet\dotnet.exe" publish AutoDTD\DTD.sln --configuration Release --runtime win10-x86 --self-contained false @C:\TeamCity\buildAgent\temp\agentTmp\1.rsp [15:50:31][publish] in directory: C:\TeamCity\buildAgent\work\39a981e90a22aaab [15:50:31][publish] Microsoft (R) Build Engine version 16.0.462+g62fb89029d for .NET Core [15:50:31][publish] Copyright (C) Microsoft Corporation. All rights reserved. [15:50:31][publish] [15:50:34][publish] [15:50:34][publish] Build FAILED. [15:50:34][publish] 0 Warning(s) [15:50:34][publish] 0 Error(s) [15:50:34][publish] [15:50:34][publish] Time Elapsed 00:00:01.65 [15:50:34][publish] [15:50:34][publish] Process exited with code 1 [15:50:34][Step 1/9] Process exited with code 1

Failed with no warnings and no errors. This is the build service equivalent of "If you don't know what's wrong, I'm certainly not going to tell you."

[Advertisement] ProGet’s got you covered with security and access controls on your NuGet feeds. Learn more.