As mentioned in #243, I noticed that in some projects additional files (and other properties as well I guess, but that was not what I was investigating) are not recognized.
I've added created this PR, that adds a replay where the additional files are not available in the AnalyzerResult.
I noticed (so far) that EventProcessor.MessageRaised(object sender, BuildMessageEventArgs e) is triggered only for v6.0.
For the (existing) test that succeeds, only one TFM is detected, for this failing test, both v6.0 and v5.0 are added. The latter lacks the additional files, but is used to build anyway.
If change the targets to only build .NET 5.0, or for .NET 8.0 and .NET 6.0 combined, everything works just fine.
I'll update mine findings here.
For some background, I use Buildalyzer to test Roslyn Analyzers that check for issues in .NET project files, such as MS Build project files, and RESX files. Access to the additional files is the perquisite for those tests to work. See: dotnet-project-file-analyzers
As mentioned in #243, I noticed that in some projects additional files (and other properties as well I guess, but that was not what I was investigating) are not recognized.
I've added created this PR, that adds a replay where the additional files are not available in the
AnalyzerResult.EventProcessor.MessageRaised(object sender, BuildMessageEventArgs e)is triggered only for v6.0.I'll update mine findings here.
For some background, I use Buildalyzer to test Roslyn Analyzers that check for issues in .NET project files, such as MS Build project files, and RESX files. Access to the additional files is the perquisite for those tests to work. See: dotnet-project-file-analyzers