Tools: Show errors when build fails

[firrae]

Describe what is not working as expected.

EF CLI tools eat MSB3026 error message. This seems most common when forgetting to stop the application before trying to add a new migration. This should be common sense, but it's caught me a few times now just forgetting.

If you are seeing an exception, include the full exceptions details (message and stack trace).

Without verbose mode enabled

Build failed.

With verbose mode enabled:

Build FAILED.

...

cannot access the file '/Users/steven.lambe/Projects/test/test/test/bin/Debug/netcoreapp2.0/test.dll' because it is being used by another process.  [/Users/steven.lambe/Projects/test/test/test/test.csproj]
/usr/local/share/dotnet/sdk/2.1.301/Microsoft.Common.CurrentVersion.targets(4172,5): error MSB3027: Could not copy "obj/Debug/netcoreapp2.0/test.dll" to "bin/Debug/netcoreapp2.0/test.dll". Exceeded retry count of 10. Failed.  [/Users/steven.lambe/Projects/test/test/test/test.csproj]

Steps to reproduce

Include a complete code listing (or project/solution) that we can run to reproduce the issue.

Partial code listings, or multiple fragments of code, will slow down our response or cause us to push the issue back to you to provide code to reproduce the issue.

I can provide more upon further request, but it just seems like the error is getting eaten.

1. Create new project
2. Add EF Core
3. Create initial migration
4. Update DB
5. Run application
6. Modify model or context
7. Create a new migration forgetting to stop the application
8. Be greeted by an empty Build failed. message

Further technical details

EF Core version: 2.0.3
Database Provider: MySql.Data.EntityFrameworkCore
Operating system: Mac OSX
IDE: VS 2017 Mac 7.5.3

EDIT: Correct error message.

[bricelam]

What is your expectation? To see the specific error message without adding --verbose?

[firrae]

@bricelam In general yes. Something along the line of Build Failed: Error MSB3026. I think it would at least be able to get people moving in the correct direction faster than having to re-run their command with verbosity turned on.

[ajcvickers]

Discussed in triage: we will try to surface the message, or if this is not possible (e.g. in PMC) then at least tell them where to look.

[firrae]

That seems fair to me, at least a push in the right direction would have saved me the little bit of time and made the error a nicer one to navigate. Thanks for looking into it 😄