Merge pull request #22 from gyk4j/20231213-add-ci-build-failure-expla…

…nation

Add explanation for CI build failures

README.md

@@ -1,13 +1,24 @@
 [![.github/workflows/dotnet-desktop.yml](https://github.com/gyk4j/wreck-net/actions/workflows/dotnet-desktop.yml/badge.svg)](https://github.com/gyk4j/wreck-net/actions/workflows/dotnet-desktop.yml)
 
-Current experiment with [GitHub Actions](https://github.com/features/actions) using [MSBuild](https://github.com/dotnet/msbuild) on 
-[legacy .NET Framework](https://dotnet.microsoft.com/en-us/learn/dotnet/what-is-dotnet-framework) project has not succeeded yet.
-
-Possible cause of failing builds:
-- Newer MS Build is unable to read or parse older Solution .sln format
-- Not setting the right path to the checked-out Solution directory and Solution .sln file on the GitHub runner
-
-CI Builds are expected to fail until a solution is found.
+> [!NOTE]
+> Current experiment with [GitHub Actions](https://github.com/features/actions) using [MSBuild](https://github.com/dotnet/msbuild) on 
+> [legacy .NET Framework](https://dotnet.microsoft.com/en-us/learn/dotnet/what-is-dotnet-framework) project has not succeeded yet.
+>   
+> Possible causes of failing builds:
+> - Newer MS Build versions are unwilling/unable to read or parse older Solution `.sln` and Project `.csproj` format
+>   i.e. Microsoft might have mandated users to upgrade their Solution/Project files to newer Visual Studio format
+> - ~~Not setting the right path to the checked-out Solution directory and Solution .sln file on the GitHub runner~~
+>
+> Troubleshooting/checks done:
+> - Actions runner's current working directory is in the repo's root and is able to locate the `Wreck.sln` solution file
+> - The Solution is tested to build cleanly with **MSBuild** on **.NET Framework 3.5** locally on development workstation.
+> 
+> So conclusion is the Solution `.sln` and project `.csproj` files are not corrupt, but the modern **.NET Core** and
+> **.NET Standard** tools are not working well with them. Maybe Microsoft has decided to drop backward compatibility.
+>   
+> CI Builds are expected to fail with the newer **MS Build** on **Windows Server 2019**.
+> 
+> No solution is foreseeable if Microsoft does not wish to support building legacy .NET Framework 3.5 desktop projects.
 
 # A simplified C#.NET implementation of WRECK.