Closed WolfgangHG closed 1 week ago
It's currently ignoring any project package references without a version attribute. I've updated it to keep them and, lacking a version, it will match it to the first package it can find by name alone. Since there shouldn't be multiple copies with conflicting versions within the same project, that should take care of the issue.
@WolfgangHG Another workaround might be to add <CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
to the projects being documented; that does make their bin folders bigger (because all dependencies are copied there).
It seems Sandcastle cannot resolve dependencies if "Nuget Central Package Management" is used (https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management)
See attached sample: in the solution root, a file "Directory.Packages.props" enables this feature and defines a list of nuget packages that are available inside this solution and the versions of these packages:
In each csproj file, the necessary packages are defined without versions:
When building the Sandcastle project in attached sample SandcastleNuget.zip, this results in an error:
I could workaround it by adding the "Wildcard Assembly References" plugin and let it point to the exact dll version in my Nuget cache:
Is there a better workaround?