-
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
Unexpected error while generating inherited documentation #886
Comments
Normally, the warning would have provided the necessary info. However, it looks like the LogWarning() method overloads changed in MSBuild and it is picking the wrong overload when I pass a StringBuilder for the message rather than explicitly converting it to a string. Given that you're working with an old project and assuming it built without warnings before, the most likely warning causing the issue is GID0010. A member using Update: It looks like the only warning affected by this issue is actually GID0009, a circular reference warning where a method imports comments from itself or another member that's already been encountered. If it's a case where that's okay and you've been ignoring it, I'll try to have an update out this weekend that fixes it. |
That's a good lead, I'll take a look over the comments next week and try and find the circular reference. A fix would be very much appreciated, but will report back soon with an update. Thanks for all the great work! |
The new release is available that should fix the issue (v2022.1.22.0). |
We have an legacy project that uses an old version of sandcastle. Upgrading to the latest version results in an argument null exception. This looks like it's isolated to a couple of projects, as we can build the documentation for most just fine. Tracking down the issue is very difficult with the stack trace.
Would it be possible to add some details about the file/line that is being processed so that it's easier to locate the issue?
Alternatively, is it possible to debug the build process so we can see the stack trace in more detail?
The text was updated successfully, but these errors were encountered: