Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Currently if you specify JavadocPaths in a csproj parameter names will be generated. It would be incredibly useful if comments for methods/classes/fields could also be extracted and added to the generated assemblies.
Related to #7797?
Gah. Wrong link.
#7797 is only about javadoc format difference (it seems, between 6 and 7) and has nothing to do with this.
We would need to be able to transform any imported comments to match our API transforms, and be able to add comments where they don't exist.
*** Bug 9308 has been marked as a duplicate of this bug. ***
In a couple of releases ago, we have introduced JavaDocIndex build action for index.html of API reference (expected to have symbolic link when the doc is not under the project folder).
(Sorry I have been reviewing existing bugs and noticed it's still open.)