You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Sandcastle project documenting a C# project targeting net6.0 and net8.0, with several NuGet packages in use
the Sandcastle tools are brought in from NuGet
when using dotnet build, this works fine
when using msbuild.exe however, the GenerateReflectionInfo step fails with SHFB : error BE0043: Unexpected error detected in last build step. See build log for details.
the log has MRefBuilder : error : Unresolved assembly reference: <assembly name for dependency from NuGet package> required by <assembly being documented
It looks like SHFB is applying a .NET Framework style dependency resolution (which would require all dependencies to be in the same folder) to a .NET library (which has a My.Assembly.deps.json alongside My.Assembly.dll file describing where dependencies are located).
I would love to leave the old .NET Framework implementation of MSBuild behind, but unfortunately, Visual Studio still uses that one, so it needs to work too.
Setting CopyLocalLockFileAssemblies to true in the project being documented resolves this error, but is not a solution - it's highly undesirable to duplicate dependency DLLs all over the place.
The text was updated successfully, but these errors were encountered:
I am running into the following issue:
net6.0
andnet8.0
, with several NuGet packages in usedotnet build
, this works finemsbuild.exe
however, theGenerateReflectionInfo
step fails withSHFB : error BE0043: Unexpected error detected in last build step. See build log for details.
MRefBuilder : error : Unresolved assembly reference: <assembly name for dependency from NuGet package> required by <assembly being documented
It looks like SHFB is applying a .NET Framework style dependency resolution (which would require all dependencies to be in the same folder) to a .NET library (which has a
My.Assembly.deps.json
alongsideMy.Assembly.dll
file describing where dependencies are located).I would love to leave the old .NET Framework implementation of MSBuild behind, but unfortunately, Visual Studio still uses that one, so it needs to work too.
Setting
CopyLocalLockFileAssemblies
totrue
in the project being documented resolves this error, but is not a solution - it's highly undesirable to duplicate dependency DLLs all over the place.The text was updated successfully, but these errors were encountered: