Treat files that don't compile as errors. #1311
Conversation
|
So, I read through the linked issue and have the same feeling you do: that CSharpier used to do this before and we changed it on purpose. Could you confirm that the behavior of CSharpier.MsBuild doesn't change as a result of this? I think there used to be an issue where CSharpier would stop be build before MsBuild go to the actual compile stage and we would only see the CSharpier errors and not the actual compiler errors. |
|
Could you please merge it and update the tool? I need it to properly use it with aider. |
I did a bit of digging on my phone and there was this issue - #957 - and the fix appears to be ignoring the output of csharpier when run via msbuild. I'll confirm that to be sure. Good call out! |
I'm not sure what aider is but I'm hoping to have a new release out within a week or two. |
… treated as errors by csharpier. There didn't appear to be a good way to get msbuild happy with the different possible outcomes without adding the flag to treat compilation errors as warnings. I tried using IgnoreStandardErrorWarningFormat and IgnoreExitCode in different combinations based on if CSharpier_Check was true or false but couldn't get every scenario working.
|
@shocklateboy92 you were correct that msbuild would be unhappy with this. Based on everything I just did I think #957 was about suppressing the warning output. The compilation failures would show up as a warning followed by an error without those changes. Getting msbuild happy with this change required adding a flag. I couldn't find another way to do it. |
closes #1131