xmldoc2md icon indicating copy to clipboard operation
xmldoc2md copied to clipboard

Tool to generate markdown from C# XML documentation

Results 15 xmldoc2md issues
Sort by recently updated
recently updated
newest added

Hello, I encountered a problem when generating documentations with `` tags. Currently xmldoc2md treats these tags as "regular" tags and takes innerText instead of the `name` attribute. This means that...

Currently given a method which returns a wrapped value, this tool generates a link to the documentation for the wrapper leaving no link to the wrapped object's documentation. Unless you...

Just added the tool to a project and tried running it, but it fails with this error: ``` Generation started: Assembly: Project.Edge.Controller Unable to generate documentation: Unable to load one...

- Library update for better compatibility (McMaster.Extensions.CommandLineUtils) - feat: changed a back button on each page with custom text - feat: add a link for back button - feat: Add...

Line `File.WriteAllText(Path.Combine(@out, $"{indexPageName}.md"), indexPage.ToString());` in `program` generates the error: `Unable to generate documentation: Object reference not set to an instance of an object.` when converting a type without a namespace....

There's any way to generate the markdown files into folders based on the namespace? If not, what do you think about having an argument `--namespace-folders` to do it? I'm happy...

It would be interesting to have a way to extend the framework with other output formats. The idea comes from the fact that after trying to use the markdown files...

In the [just-the-docs](https://github.com/just-the-docs/just-the-docs) template there is configuration through front matter. Is it possible to add in a parameter to add in front matter. In my use case there is a...

The XML documentation markup ``/// `` does not produce any documentation. Observed behavior: No documentation is generated Expected behavior: The generated documentation should be the inherited documentation.

As discussed in #19 generation docs fails if some dependencies don't end-up with a dll in the `OutDir`. The golden path would of course be to resolve the nuget dependencies...