-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documenting a net8.0
project when using msbuild.exe
#1052
Comments
Can you attach an example demonstrating the issue? |
Will try. An initial barebones case seems to work (although obviously complaining it can't resolve outside references). Will try to get it as close to my real case as possible to see if it's any particular setting that triggers it. |
I can't seem to reproduce it easily from scratch so will have to spend a lot more time trying to reduce the solution where I do have the issue to something I can share, and I don't currently have that time. Feel free to mark as On Hold for the time being (same for #1051). |
Thanks to #1057 I now have a reproduction test case.
|
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: