Skip to content

Releases: phmonte/Buildalyzer

3.2.6

23 Dec 17:46
Compare
Choose a tag to compare
  • 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

14 Dec 16:58
Compare
Choose a tag to compare
  • 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

17 Aug 18:57
Compare
Choose a tag to compare
  • 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.

3.2.2

26 May 15:14
Compare
Choose a tag to compare

3.2.1

05 May 01:14
Compare
Choose a tag to compare
  • Sets SolutionFilePath in the Workspace Solution when it's available (#177, thanks @markrendle)
  • Fixed ProjectAnalyzer exceptions when the solution file is not in the source root (#175, #176, thanks @psfinaki)
  • Fixed a small QOL change needed when using Buildalyzer for F# (#172, thanks @dukedagmor)
  • Fixed bug when PackageReference contains the name of a package in Update instead of Include (#170, #171, thanks @eNeRGy164)
  • Refactored Buildalyzer.Workspaces so a Microsoft.CodeAnalysis.VisualBasic.Workspaces reference is not needed when not using Visual Basic features (#168, #169, thanks @svick)

3.2.0

12 Jan 15:14
Compare
Choose a tag to compare
  • Refactored ProjectItem to an interface IProjectItem for easier mocking/testing (#161, #162, thanks @fbd)
  • Fixed .NET Framework TFM identification for .NET Core/.NET 5 and others (#163, #164, thanks @slang25)
  • Automatically adds project references that didn't originally exist in the manager when building a Roslyn workspace (#159, #160, thanks @slang25)

3.1.1

20 Dec 19:52
Compare
Choose a tag to compare

3.1.0

30 Oct 20:50
Compare
Choose a tag to compare
  • Added SourceFiles and References for F# projects (#146, thanks @dukedagmor)
  • Fixed an inconsistency between Buildalyzer and MSBuild by adding a trailing directory separator to the solution path (#147, #148, thanks @laurenceSaes)

3.0.1

24 Jun 01:29
Compare
Choose a tag to compare

3.0.0

21 May 17:00
Compare
Choose a tag to compare
  • 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)