Cleanup and release prep

phmonte · Jan 20, 2022 · 4adcd95 · 4adcd95
1 parent a71b5ba
commit 4adcd95
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 2 deletions.
diff --git a/ReleaseNotes.md b/ReleaseNotes.md
@@ -1,3 +1,9 @@
+# 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).

diff --git a/tests/Buildalyzer.Tests/Integration/SimpleProjectsFixture.cs b/tests/Buildalyzer.Tests/Integration/SimpleProjectsFixture.cs
@@ -237,8 +237,10 @@ public void MultiTargetingBuildAllTargetFrameworksGetsSourceFiles()
             IAnalyzerResults results = analyzer.Build();
 
             // Then
-            results.Count.ShouldBe(2);
-            results.TargetFrameworks.ShouldBe(new[] { "net462", "netstandard2.0" }, true, log.ToString());
+            // Multi-targeting projects product an extra result with an empty target framework that holds some MSBuild properties (I.e. the "outer" build)
+            results.Count.ShouldBe(3);
+            results.TargetFrameworks.ShouldBe(new[] { "net462", "netstandard2.0", string.Empty }, true, log.ToString());
+            results[string.Empty].SourceFiles.ShouldBeEmpty();
             new[]
             {
                 // Linux and Mac builds appear to omit the AssemblyAttributes.cs file