Warning BE0066 ResolveReferenceLinksComponent #1025
-
|
We include a third party (CefSharp) documentation file in our help as we extend one of their controls. On building I get several 'Unknown reference link' target warnings because the CefSharp documentation is referencing one of their private methods, OnAfterBrowserCreated:
It also throws the same warning in our extended component:
I've tried putting all third party sources in a separate help file and linking to it using the Additional Reference Links plug-in and setting all links to none, but the warnings remain. I can't use the API filter to exclude Company.WebBrowser and CefSharp.WinForms.ChromiumWebBrowser as this creates lots of unknown reference link targets from other areas of our API. We don't include private members in our help. Is there any other way around this that I maybe missing? Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Are you including the private members in the linked project? If not, it won't be there to ignore. |
Beta Was this translation helpful? Give feedback.
-
|
I wasn't, turning on private members in the linked project has removed these warnings:
But I'm still getting the warnings from our type that extends ChromiumWebBrowser: Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Do you think the only solution is to also turn on private members in our main help project? That's the only way it'll see OnAfterBrowserCreated I guess? |
Beta Was this translation helpful? Give feedback.
-
|
No, you'd end up with a lot of unwanted members you'd have to remove with the API filter. More likely than not, it's referenced in a public member's comments. If you can track it down, you could create a local XML comments file with a copy of the comments for that member with the link removed. It would override the inherited comments. |
Beta Was this translation helpful? Give feedback.
-
|
There was no reference to it in our code, but I've overridden the method that references the private member in our class, and copied the documentation with the link removed as suggested. This has fixed it. Many thanks for your help. |
Beta Was this translation helpful? Give feedback.
No, you'd end up with a lot of unwanted members you'd have to remove with the API filter. More likely than not, it's referenced in a public member's comments. If you can track it down, you could create a local XML comments file with a copy of the comments for that member with the link removed. It would override the inherited comments.