Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Binary Logging in VSTS (CI) builds
See original GitHub issueCan we use BinaryLogger to log the builds in VSTS or others?
It was useful when testing the build process of my projects.
I already added the option in the response files but Is it safe to copy the files to logs directory of VSTS (if there is one)?
BinaryLogger records everything that msbuild gets, including any sensitive env values like API Keys, Passcodes, etc…
Is there anyway to exclude those sensitive env variables in a build?
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Enhance Integrated CI and CD in Azure Pipelines as Code ...
Turn on binary logging in MSBuild so that you receive exhaustive structured logs from the build process. You can visualize these logs using ......
Read more >Logging commands - Azure Pipelines
Logging commands are how tasks and scripts communicate with the agent. ... #!/bin/bash echo "##vso[task.setvariable variable=testvar ...
Read more >MSBuild Log Viewer
Use the Project System Tools Visual Studio extension to record binary logs of IDE and design-time builds. See more information about design-time builds...
Read more >Creating binary logs from Visual Studio - Matt Lacey
It's possible (and well documented) to save detailed and binary log files when compiling code with MSBuild. But, if you are getting different ......
Read more >Detecting Double-Writes in MSBuild using the binlog
Open the console with MSBuild in the path: Open developer prompt for Visual Studio. Run msbuild with /bl flag to generate the binary...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
https://github.com/Microsoft/msbuild/issues/3432
No current plans. The problem is that even if you exclude certain variables from the binlog, they still might be used in some expressions, and I don’t want to create a false sense of security. Better be on the safe side.
One interesting idea would be to mark the environment variables actually used by MSBuild and only include those. But that’s an MSBuild request.