3.0.0

• Added support for specifying additional MSBuild arguments via EnvironmentOptions.Arguments.
• Updated the MSBuild.StructuredLogger package to version 2.1.133
• Updated MSBuild packages to 16.5.0 (#140, thanks @colombod)
• Updated Microsoft.CodeAnalysis packages to 3.6.0
• The result of these package updates is that while Buildalyzer itself targets .NET Standard 2.0, any consuming application will need to target either .NET Core 2.1 or .NET Framework 4.7.2 (or higher)

2.6.0

• [Refactoring] Refactored key classes into interfaces for easier testing (#132, thanks @richardwerkman)

2.5.1

• [Fix] Removed the explicit encoding parameter when generating a SourceText in Buildalyzer.Workspaces (#128)
• [Fix] Fixes a race condition in ProcessRunner in Process.WaitForExit() calls (#125, thanks @duncanawoods)

2.5.0

• [Fix] Fix for finding the default SDK in some scenarios due to differences in output from dotnet (#120, thanks @patriksvensson)
• [Refactoring] Updates Microsoft.CodeAnalysis dependencies in Buildalyzer.Workspaces (#124, thanks @farnyser)
• [Feature] Support for F# projects (#123)

2.4.0

• [Fix] Removes IProjectTransformer since Buildalyzer no longer feeds project files to the MSBuild API (#114)
• [Feature] Adds back project filtering (#118)
• [Fix] Added "System.Reflection.TypeExtensions" as a direct dependency for .NET Framework consumers (#116)
• [Fix] Disable the COREHOST_TRACE environment variable (#115, thanks @sapsari)

2.3.0

• [Feature] Package references are now available directly in ProjectFile (#111, thanks @eNeRGy164)
• [Feature] Better future-proof MSBuild path discovery (#106, thanks @colombod)
• [Fix] Fixes for csc arguments parser (#100, thanks azyobuzin)

2.2.0

• [Fix] Several fixes for parsing the csc command line arguments from the build log (#89)
• [Feature] Passes all defined constants from the build to Roslyn (#86)
• [Feature] Now uses a single MSBuild submission and defers restore phase to MSBuild (#66)
• [Feature] Better processing of dotnet console output (#94, thanks @jonstelly)
• [Feature] Better support for two-phase builds like Razor projects (#92, #93, thanks @jonstelly)
• [Feature] Parallelize project builds when creating a Roslyn workspace (#91, thanks @jonstelly)
• [Refactoring] Scopes project ID cache when creating Roslyn workspaces to AnalyzerManager (#87. #88, thanks @wadinj)
• [Feature] Adds support for setting a custom dotnet.exe path (#84, thanks @itn3000)
• [Fix] Avoid exceptions when overwriting existing keys in EnvironmentOptions (#83, thanks @itn3000)
• [Feature] Adds AnalyzerResult.PackageReferences to easily access project package references (#82, thanks @mholo65)

2.1.0

• [Feature] Adds AnalyzerManager.Analyze() support for reading MSBuild binary log files
• [Fix] Fix for pipe communication problems on Linux

2.0.1

• [Fix] Fix for hang when the MSBuild process fails to start or logger doesn't connect (#78)

2.0.0

• [Breaking Change] [Refactoring] Entire API...again. Consider this the "if at first you don't succeed" release.
• [Refactoring] Now uses MSBuild directly by launching out-of-process MSBuild instances instead of the API - if you can build it, Buildalyzer should be able to
• [Refactoring] Reduced build methods to just ProjectAnalyzer.Build() and overloads - every build builds now builds every target framework unless otherwise specified and always returns an AnalyzerResults
• [Refactoring] AnalyzerResult build results are now limited to what we can pull out of MSBuild logs (which is surprisingly a lot) - file an issue if you're missing something you used to get from the old MSBuild API results