Releases: mono/api-doc-tools
Releases · mono/api-doc-tools
mdoc 5.7.4.9
fixes crash on attached properties that have overloads on get or set
mdoc 5.7.4.8
This release includes the following changes
param
nodes will no longer 'lose' documentation.Parameter
nodes will now have more consistentIndex
andFrameworkAlternate
attributes when necessary.- #413 - framework names are now sorted by alpha in the
fx-bootstrap
subcommand. - #367 - attached property support now includes read or write only attached properties.
mdoc 5.7.4.7
- #396 - attributes should no longer see empty
FrameworksAlternate
attributes. - #300 - mdoc now deletes type files that no longer exist, rather than renaming them to
*.xml.remove
. - The previous release had an issue where type files would be removed, so please consider the release notes/features from that release here as well:
- #291 - Fixes an issue with property indexing in frameworks mode. Member nodes that were previously incorrectly indexed will now be replaced with a new and correct node.
- #249 - added C# signature support for
ref readonly
andref return
(Thanks @TianqiZhang!) - Now supports resolving assemblies with non-lowercase extensions (Thanks @mattleibow!)
mdoc 5.7.4.6
- #291 - Fixes an issue with property indexing in frameworks mode. Member nodes that were previously incorrectly indexed will now be replaced with a new and correct node.
- #249 - added C# signature support for
ref readonly
andref return
(Thanks @TianqiZhang!) - Now supports resolving assemblies with non-lowercase extensions (Thanks @mattleibow!)
mdoc 5.7.4.5
- Improves logging - Log will now be more explicit about what assembly it's currently processing, and include the assembly name and path if an exception is thrown (for example, if it can't resolve a type)
- Resolver is now removing default cecil search paths - due to re-prioritizing the search paths in the last release, if the program's working directory is set to something else (as would be the case on a CI server), the
.
would result in unexpected assembly resolutions.
mdoc 5.7.4.4
- #357 - fixes an issue with the assembly resolver cache that was causing cross-framework type/member contamination.
- This also changes the behavior of resolving assembly references with 0.0.0.0 as the version … previously mdoc would load the highest version assembly in that case, now it loads the first one it encounters, starting in the framework folder, then in the framework dependency folder, then in the global dependency folder(s) passed to mdoc, then in the system folders.
- Also includes a fix to reduce the possibility of duplicating a docid in the frameworks index file.
mdoc 5.7.4.3
This release fixes issue #388
mdoc 5.7.4.2
mdoc 5.7.4.1
This release improves mdoc's ability to resolve framework assemblies (#363)
mdoc 5.7.4
- #334 - all interfaces are now listed
- #103 - all assemblies in a framework are now listed in the framework index file
<Assemblies> <Assembly Name="DocTest-DropNS-classic" Version="0.0.0.0" /> <Assembly Name="DocTest-addNonGeneric" Version="0.0.0.0" /> </Assemblies>
- #357 - stubbing out new types uses the loaded assembly to resolve the framework, rather than the resolved assembly (which might be different due to type exports)