You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you use the MSBuild /bl command line option, by default the ProjectImports option is set to "Embed", which means you get the source text of project files, including all imported projects and target files, embedded in the .binlog. If this information is embedded in the .binlog, then MSBuild Structured Log Viewer makes it easy to see the definition for targets that are run, or search through the source files, etc.
It would be very helpful if the VS extension would also include this information in the .binlogs it creates by default.
The text was updated successfully, but these errors were encountered:
Finally got to take a look at this but there's an issue... the problem is that the ProjectImports option depends on the build doing the evaluation and the build in one go. In the case of VS, evaluation and builds are done separately -- we evaluate the project when we open it, and then we later do design-time and regular builds separately. What I'm seeing is that with the option set, you only get the project file itself, no imports, which is of iffy usefulness. @KirillOsenkov any ideas?
When you use the MSBuild
/bl
command line option, by default the ProjectImports option is set to "Embed", which means you get the source text of project files, including all imported projects and target files, embedded in the .binlog. If this information is embedded in the .binlog, then MSBuild Structured Log Viewer makes it easy to see the definition for targets that are run, or search through the source files, etc.It would be very helpful if the VS extension would also include this information in the .binlogs it creates by default.
The text was updated successfully, but these errors were encountered: