-
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
Support for Nuget Central Package Management #1057
Comments
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 |
I can confirm that my help file builds again with recent Sandcastle version. |
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?
The text was updated successfully, but these errors were encountered: