I'm not sure if this should be changed. If you look at csc.exe, cl.exe, and msbuild.exe, they all output their errors to stdout. By convention, it seems like WiX's current behavior is correct.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Maybe it's correct by Microsoft convention, in my opinion it's not reasonable.
I've made an extension that harvests light dependencies, prints them to standard output and and makes light to finish with an error. The error is also printed to standard output and gets mixed with the dependencies. I solved the problem by printing the dependencies to the error stream.
In general it seems to be rather unconventional solution.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
However, the convention in this case is defined by the tools that the WiX toolset works with: csc.exe, cl.exe, vc.exe and MSBuild. MSBuild defines how errors and warnings are supposed to be output (namely the file path(line number) : error/warning ABBREVIATION Err# : message).
I don't think we should deviate from this convention.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure if this should be changed. If you look at csc.exe, cl.exe, and msbuild.exe, they all output their errors to stdout. By convention, it seems like WiX's current behavior is correct.
Maybe it's correct by Microsoft convention, in my opinion it's not reasonable.
I've made an extension that harvests light dependencies, prints them to standard output and and makes light to finish with an error. The error is also printed to standard output and gets mixed with the dependencies. I solved the problem by printing the dependencies to the error stream.
In general it seems to be rather unconventional solution.
I hear you.
However, the convention in this case is defined by the tools that the WiX toolset works with: csc.exe, cl.exe, vc.exe and MSBuild. MSBuild defines how errors and warnings are supposed to be output (namely the file path(line number) : error/warning ABBREVIATION Err# : message).
I don't think we should deviate from this convention.