Bump Buildalyzer from 3.2.1 to 4.1.6

[dependabot]

Bumps Buildalyzer from 3.2.1 to 4.1.6.

Release notes

Sourced from Buildalyzer's releases.

4.1.6

• Fixed a NullReferenceException for F# projects (#216, thanks @​psfinaki).

4.1.5

• Added a BuildEnvironment.NoAutoResponse option to control whether the /noAutoResponse argument is set, with a default of true to avoid processing .rsp files that could conflict with Buildalyzer (#211).
• Add API to retrieve compiler command-line and arguments (#212, #213, thanks @​siegfriedpammer).

4.1.4

• Added support for Visual Basic projects (#207, thanks @​cslong).
• Added support for the additionalfile compiler argument as IAnalyzerResult.AdditionalFiles (#200).

4.1.3

• Ensured all project references are distinct (#203, #204, thanks @​Mingxue008, @​Therzok, and @​slang25).

4.1.2

• Updated MsBuildPipeLogger to 1.1.6.
• Updated Microsoft.CodeAnalysis to 4.1.0.

4.1.1

• Added SourceLink support.

4.1.0

• Updated Buildalyzer.Logger to target .NET Standard 2.0.
• Updated MsBuildPipeLogger references to version 1.1.4.

4.0.0

• Updated Buildalyzer to target .NET Core 3.1 (#197, #189, thanks @​AdaskoTheBeAsT and @​slang25).
• Made AnalyzerResults.TargetFrameworks and related properties deterministically ordered (#198, thanks @​0xced).

3.2.8

• Reverted UseAppHost back to defaults for Buildalyzer builds in favor of setting ComputeNETCoreBuildOutputFiles instead so that self-contained application builds still work (#194, #185, #187).
• Added ability to bypass MSBuild when using .NET Core/.NET (I.e. the dotnet command) so that other commands like publish can be invoked (#195, thanks @​echalone).
• Added support for analyzing build logs that don't set a TargetFrameworkMonitor (I.e. C++ projects) (#196, thanks @​echalone).

3.2.7

• Fixed MSBuild polling in Visual Studio directories when Visual Studio 2022 is installed since it now installs into the normal "Program Files" folder (as opposed to the x86 one).

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.

... (truncated)

Changelog

Sourced from Buildalyzer's changelog.

4.1.6

• Fixed a NullReferenceException for F# projects (#216, thanks @​psfinaki).

4.1.5

• Added a BuildEnvironment.NoAutoResponse option to control whether the /noAutoResponse argument is set, with a default of true to avoid processing .rsp files that could conflict with Buildalyzer (#211).
• Add API to retrieve compiler command-line and arguments (#212, #213, thanks @​siegfriedpammer).

4.1.4

• Added support for Visual Basic projects (#207, thanks @​cslong).
• Added support for the additionalfile compiler argument as IAnalyzerResult.AdditionalFiles (#200).

4.1.3

• Ensured all project references are distinct (#203, #204, thanks @​Mingxue008, @​Therzok, and @​slang25).

4.1.2

• Updated MsBuildPipeLogger to 1.1.6.
• Updated Microsoft.CodeAnalysis to 4.1.0.

4.1.1

• Added SourceLink support.

4.1.0

• Updated Buildalyzer.Logger to target .NET Standard 2.0.
• Updated MsBuildPipeLogger references to version 1.1.4.

4.0.0

• Updated Buildalyzer to target .NET Core 3.1 (#197, #189, thanks @​AdaskoTheBeAsT and @​slang25).
• Made AnalyzerResults.TargetFrameworks and related properties deterministically ordered (#198, thanks @​0xced).

3.2.9

• Added additional logging for Roslyn workspace creation in Buildalyzer.Workspaces.

3.2.8

• Reverted UseAppHost back to defaults for Buildalyzer builds in favor of setting ComputeNETCoreBuildOutputFiles instead so that self-contained application builds still work (#194, #185, #187).
• Added ability to bypass MSBuild when using .NET Core/.NET (I.e. the dotnet command) so that other commands like publish can be invoked (#195, thanks @​echalone).
• Added support for analyzing build logs that don't set a TargetFrameworkMonitor (I.e. C++ projects) (#196, thanks @​echalone).

3.2.7

• Fixed MSBuild polling in Visual Studio directories when Visual Studio 2022 is installed since it now installs into the normal "Program Files" folder (as opposed to the x86 one).

... (truncated)

Commits

• 6855958 Release notes
• d20808d More clear like this
• 071979f Fixed an NullReferenceException for F# projects
• da86d32 Removing the Functions project from the test solution
• 478fd1c Updated release notes
• cb0dd28 Added failing tests for Functions apps but couldn't get them to work (https:/...
• 7ce6355 Remove unnecessary 'bool initialCommand' parameter from EnumerateCommandLineP...
• 611e4a0 Use vbc options in vbc test cases.
• b8cb48f Fix #212: Add API to retrieve compiler command-line and arguments from IAnaly...
• d34d9c5 Ignores rsp files by default (#211)
• 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)

[dependabot]

Superseded by #115.