Dave Glick

Just checking in - have you had any luck with the suggestions above?

Buildalyzer doesn't actually process the project file on its own (at least not beyond _very_ rudimentary parsing to figure out how to call MSBuild), and the values in `IAnalyzerResult` come...

> where has the fix from #40 gone? It was lost during the big 2.x rewrite. While it's important to have the option, I didn't want to make it too...

@faldor20 See the comment above - did you happen to interact with Roslyn workspaces? If so, that gives me somewhere to start. This issue seems to have flown under my...

> I could look at PackageReferences, but these are not parsed in the ProjectFile class. It only shows if there are any references. Thanks for the PR! I'm assuming that...

:thumbsup: I'll leave this issue open as a feature request and we can add more support if anyone figures out what to look at.

I'm not sure I'm totally following the problem you're having. Can you provide a little more information? - How are you calling Buildalyzer (code samples, etc.)? - What is your...

What an interesting scenario. It never occurred to me this might be a problem, but it makes total sense. I guess the challenge is knowing which one to pick -...

Interesting, I haven't seen this particular error before. It's almost like your app has a reference to `MsBuildPipeLogger` but the logger isn't being loaded into your assembly context. What happens...

That actually doesn’t look like an error from my code - I’m going to guess it’s coming from the MSBuild.StructuredLogger package which is currently at 2.1.113. The latest of that...