You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a multi-targeting library. It targets netstandard2.0, net8.0, net8.0-windows and net8.0-macos. How do I generate API docs such that the docs include APIs that are unique to a particular TFM? Right now, the docs omit the net8.0-macos specific APIs at least.
In addition to the requirement of including the union of all APIs across all TFMs, I'd very much like the documentation to mention which TFMs support each API, and/or a way for users to filter the displayed APIs to a particular TFM.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a multi-targeting library. It targets netstandard2.0, net8.0, net8.0-windows and net8.0-macos. How do I generate API docs such that the docs include APIs that are unique to a particular TFM? Right now, the docs omit the net8.0-macos specific APIs at least.
In addition to the requirement of including the union of all APIs across all TFMs, I'd very much like the documentation to mention which TFMs support each API, and/or a way for users to filter the displayed APIs to a particular TFM.
Beta Was this translation helpful? Give feedback.
All reactions