With .NET 8 SDK, `BinaryFormatter` seems to be disallowed, resulting in some plugin failures about shfb

[EWSoftware]

The URL cache file might be corrupted. Delete the %USERPROFILE%\Local Settings\Application Data\EWSoftware\Sandcastle Help File Builder\Cache folder and it will rebuild it.

[Zastai]

Strangely I'm getting an error with the .NET SDK 6.0.25 too (which does not disable BinaryFormatter), but there the root exception is different:

Attempting to deserialize an empty stream.
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream)
   at Sandcastle.Tools.BuildComponents.ResolveReferenceLinksComponent.CreateMemberIdResolver(XPathNavigator configuration)
   at Sandcastle.Tools.BuildComponents.ResolveReferenceLinksComponent.Initialize(XPathNavigator configuration)
   at SandcastleBuilder.Utils.BuildEngine.BuildAssemblerInternal.LoadComponent(XPathNavigator configuration)

[EWSoftware]

I'm aware of the issue. The cache used to contain resolved reference links is stored in a binary format. I've found a way to generate the links without the web service thus removing the need for the cache altogether. It may be a few weeks before I get it done and release an update though.

[Zastai]

Any idea on what the second issue (empty stream) could be?

I am running into that on every attempt to build any SHFB project, even with msbuild.exe (which uses .NET Framework, so no BinaryFormatter issue).
Even with the (now very old) SHFB version we're using in CI:

  BuildAssembler (v2020.3.6.0)
  Copyright c 2006-2020, Microsoft Corporation, All Rights Reserved.
  Portions Copyright c 2006-2020, Eric Woodruff, All Rights Reserved.
  Loading configuration...
BuildAssembler : error :  [C:\path\to\project\output\Release\Website\BuildTopics.proj]
BuildAssembler : error : BuildAssemblerCore: An unexpected error occurred while attempting to create the build component 'Resolve Reference Links Component'. The error message is: Attempting to deserialize an empty stream. [C:\path\to\project\output\Release\Website\BuildTopics.proj]
BuildAssembler : error :  [C:\path\to\project\output\Release\Website\BuildTopics.proj]
BuildAssembler : error : BuildAssemblerCore: An unexpected error occurred while attempting to create the build component 'Multi-format Output Component'. The error message is: See log for details [C:\path\to\project\output\Release\Website\BuildTopics.proj]
BuildAssembler : error :  [C:\path\to\project\output\Release\Website\BuildTopics.proj]
BuildAssembler : error : BuildAssemblerCore: An unexpected error occurred while attempting to create the build component 'Switch Component'. The error message is: See log for details [C:\path\to\project\output\Release\Website\BuildTopics.proj]
Done Building Project "C:\path\to\project\output\Release\Website\BuildTopics.proj" (default targets) -- FAILED.

Unfortunately, there's no logging (even with -v:d) that would indicate what stream it's trying to read (a file? a url?).

It does seem specific to my machine at the moment (a colleague using the same VS2022 version and .NET 8SDK installed is able to build without error), making it even weirder. I did try clearing my temporary files folder as well as my nuget cache in case there was an issue there, with no change.

[Zastai]

That was it, thanks. Is there a way to inhibit that file's use, or configure its location, from the project file?

I'm not sure I like the idea that a single broken file can break all builds on a machine; that could significantly disrupt CI/CD.

[Zastai]

Note that I'm now getting:

BuildAssembler : warning : ResolveReferenceLinksComponent: ... Member ID URL resolver service failed.  No further look ups will be performed for this build. [...\BuildTopics.proj]
BuildAssembler : warning : Reason: The remote server returned an error: (403) Forbidden. [...\BuildTopics.proj]

[EWSoftware]

The service (https://xref.docs.microsoft.com) is currently returning an error. It may be temporary or Microsoft may have shut it down. I know the latest release of DocFX no longer uses it though older version still would. The old MSDN web service stayed up for quite a while but became unreliable which is why I switched away from it. Eventually the same will happen to the latest service which is why I'm working on moving away from it and going with code-based generation of the links since they use a deterministic format now.

[Zastai]

@EWSoftware Hi. Do you have a rough idea of when a release could be published (including the 8.0.0 version of SHFB.NET)?

[EWSoftware]

My free time has been rather limited of late. I'm going to try again this weekend to get it published. I've got Monday off so should be able to get it out.

[EWSoftware]

Version 2024.2.18.0 is now available along with the updated reflection data set packages.

[Zastai]

Awesome! Thanks a lot.