Open danmoseley opened 3 years ago
This is where that error is thrown. As you can see, we're already throwing just the message, but "e.Message already contains the stack trace" as indicated in the comment. I don't think it's worth it to parse the message to extract just the actual message part; ultimately, this gives the user access to all the information they need, just with some extra.
Reasonable to close?
The bug then is that the exception message contains the stack. I agree it's low priority.
From a customer using Version 17.0.0 Preview 5.0 [31807.328.d17.0], their machine got into some bad state, and they get this output.
Assuming this is not indicating a bug in MSBuild, but rather a bad machine state, the exception should be caught so that only the error message is shown.