Dave Glick

Love this idea! > What we thought is to ask the contributors to react with 👍 on the CLA Pull request comment While that seems like a great user experience...

The security restriction makes sense for arbitrary action, but hopefully they come up with some kind of trusted flag or other way to mark the action as having access. In...

Unfortunately, assembly loading can be tricky and the location of the logging assembly could be in a few places depending on platform, delivery, etc. That's why `Assembly.Location` works well here...

> Would accept a PR that implements this feature? Yeah, absolutely - Buildalyzer has an intentionally narrow scope, but this feature sounds like it fits right in with the goal...

New release of Buildalyzer with this feature went out last night - thanks again!

Yeah, I could swear I worked on this exact thing not too long ago (though it's been a crazy summer for me, so it's also just as likely I'm thinking...

I've continued to look at this and can't figure out why the Functions build tooling continues to fail. I strongly suspect it's related to the way Buildalyzer sets certain MSBuild...

> You can disable node reuse with the command line switch `/nodeReuse:false` or with the environment variable `MSBUILDDISABLENODEREUSE=1`. Having just searched for docs regarding node reuse, this issue was helpful....

Never mind, just ran across https://github.com/Microsoft/msbuild/issues/339 which explains the situation nicely. I was having some problems with it reusing nodes even after setting `MSBUILDDISABLENODEREUSE` but it looks like that's because...

Not quite - that will crawl the node tree, writing to the TextWriter (and underlying Stream) all at once. What I'm thinking about is reading as a stream on the...