(deps): Bump Buildalyzer from 3.2.2 to 3.2.6

[dependabot]

Bumps Buildalyzer from 3.2.2 to 3.2.6.

Release notes

Sourced from Buildalyzer's releases.

3.2.6

• Specifies an encoding for source text in Buildalyzer.Workspaces to avoid CS8055 errors ("Cannot emit debug information for a source text without encoding") when compiling the workspace (#128).

3.2.5

• Added a strongly-typed PreprocessorSymbols collection to AnalyzerResults and used it to flow constants through to Buildalyzer.Workspaces for .NET 5 and up projects (#191, #192, thanks @​richardwerkman).
• Set UseAppHost to false for Buildalyzer builds since there's no need to create native executables for analysis (#185, #187, thanks @​slang25).
• Added a test project for checking .NET 6 compatibility (#185, #186, thanks @​bernd5).

3.2.3

• Fixed a bug where Buildalyzer.Workspaces would not add transitive references to projects in the Roslyn workspace (#181).
• No longer attempts to add F# projects from a solution to the Roslyn workspace in Buildalyzer.Workspaces which causes an exception in Roslyn.
• Updated structure logging support to the latest package providing binlog version 14 parsing (#184).
• Updated Microsoft.CodeAnalysis package references in Buildalyzer.Workspaces to 3.11.0.
• Updated MSBuild libraries for programmatic use by Buildalyzer to 16.10.0.

Changelog

Sourced from Buildalyzer's changelog.

3.2.6

• Specifies an encoding for source text in Buildalyzer.Workspaces to avoid CS8055 errors ("Cannot emit debug information for a source text without encoding") when compiling the workspace (#128).

3.2.5

• Added a strongly-typed PreprocessorSymbols collection to AnalyzerResults and used it to flow constants through to Buildalyzer.Workspaces for .NET 5 and up projects (#191, #192, thanks @​richardwerkman).
• Set UseAppHost to false for Buildalyzer builds since there's no need to create native executables for analysis (#185, #187, thanks @​slang25).
• Added a test project for checking .NET 6 compatibility (#185, #186, thanks @​bernd5).

3.2.4

• Updated structured logging library to consolidate MSBuild and binary logging types (internal change, should be no impact to consumers).

3.2.3

• Fixed a bug where Buildalyzer.Workspaces would not add transitive references to projects in the Roslyn workspace (#181).
• No longer attempts to add F# projects from a solution to the Roslyn workspace in Buildalyzer.Workspaces which causes an exception in Roslyn.
• Updated structure logging support to the latest package providing binlog version 14 parsing (#184).
• Updated Microsoft.CodeAnalysis package references in Buildalyzer.Workspaces to 3.11.0.
• Updated MSBuild libraries for programmatic use by Buildalyzer to 16.10.0.

Commits

• 325949a Sets an encoding for workspace source text (#128)
• ba22694 Fixing up some small bugs including support for .NET 5/6 dotnet --info calls
• 5ebe40f Ignore case when looking in _cscCommandLineArguments
• 14e6a8c Remove submodules
• 487bcdb Add PreprocessorSymbols to analyserResult
• fd3d5f0 UseAppHost = false
• 78f4427 added hello-world test case for net 6.0 projects
• e30d447 Updating StructuredLogger to fix type duplication problems
• a219748 Version bump
• 93e2dc0 Added tests for different binlog versions
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[hyabean]

@asbjornu @arturcic

The "or" should be "and". Some unit tests failed on local machines.
Why not use some config for all targetFrameworks?

[arturcic]

Why not use some config for all targetFrameworks?

What do you mean?

[hyabean]

Some unit tests failed on my local machine, which environment is Windows 10 and Visual Studio 2022. The reason is the Buildalyzer 3.2.5 reference to Microsoft.Build.dll version 16. So the project references to Microsoft.Build.dll version 16 and Microsoft.Build.Framework.dll version 17. But I'm confused why the CI is success.

I don't know why you use different package versions for .net core 3.1 and net5.0 in commit bb243bc
But I founded that the failed unit tests run success by replacing

    <ItemGroup Condition=" '$(TargetFramework)' == 'netcoreapp3.1' ">
        <PackageReference Include="Buildalyzer" Version="3.2.2" />
        <PackageReference Include="MSBuild.ProjectCreation" Version="6.3.3" />
        <PackageReference Include="Microsoft.Build" Version="16.9.0" />
    </ItemGroup>

    <ItemGroup Condition=" '$(TargetFramework)' == 'net5.0' ">
        <PackageReference Include="Buildalyzer" Version="3.2.5" />
        <PackageReference Include="MSBuild.ProjectCreation" Version="6.3.3" />
        <PackageReference Include="Microsoft.Build" Version="16.11.0" />
    </ItemGroup>

    <ItemGroup Condition=" '$(TargetFramework)' != 'netcoreapp3.1' or '$(TargetFramework)' != 'net5.0' ">
        <PackageReference Include="Buildalyzer" Version="3.2.5" />
        <PackageReference Include="MSBuild.ProjectCreation" Version="6.3.3" />
        <PackageReference Include="Microsoft.Build" Version="17.0.0" />
    </ItemGroup>

with

    <ItemGroup>
        <PackageReference Include="Buildalyzer" Version="3.2.5" />
        <PackageReference Include="MSBuild.ProjectCreation" Version="6.3.3" />
        <PackageReference Include="Microsoft.Build" Version="17.0.0" />
        <PackageReference Include="Microsoft.Build.Framework" Version="17.0.0" />
    </ItemGroup>

.

<PackageReference Include="Microsoft.Build.Framework" Version="17.0.0" />
is added to fix the version conflict of Microsoft.Build.Framework.dll and Microsoft.Build.

[dependabot]

Superseded by #2965.