Dave Glick

I updated the MSBuild.StructuredLogger package and added a .NET 6.0 project to the test suite. It runs okay, so I'm not seeing a repro at the moment. Are you able...

>are you publishing new version of Buildalyzer? Not yet - want to make sure the issue with .NET 6 and binary log versions is resolved before publishing. Any change you...

Please try the newly release Buildalyzer v3.2.3 package and let me know if that resolves the issues you're seeing.

I'm having a little trouble understanding the issue here. Can you provide any more details about the `InvalidOperationException` generated in this case? Is it coming from Buildalyzer directly (and if...

I just did some related work on transitive references in Roslyn workspaces in #181 which should hopefully help with the scenario here, but I still can't reproduce anything like the...

Thanks for the coffee! > So if you'll pardon me for being lazy and not walking through the Buildalyzer code...what's the secret? :) Prepare for lots of words...I could write...

I think I understand the problem, but not sure I'm following the suggested solution. If I recall we always call MSBuild, either directly or indirectly depending on if it's a...

Unfortunately there isn't a great way to do this right now (at least not that I can think of - happy for suggestions here!). Because Buildalyzer "shells out" to MSBuild...

Buildalyzer 3.0.1 is now rolling out to NuGet and should (hopefully) resolve this issue. When you get a chance can you please verify that this problem is resolved? Thanks!

> When I comment out the cancellation, I now see reliable results. Awesome! Thanks for tracking this down to a root cause - when I initially tried to reproduce I...