[preview] mdoc v5.0.0.23

This release fixes a remaining issue on #107 in frameworks mode, by improving member/xml node matching on members with modopt/modreq. Additionally, duplicate nodes found during an update that differ slightly (as in the case of members that have modopt/modreq) will now delete, rather than issuing a warning.

[preview] mdoc v5.0.0.22

• #112: Resolver now recurses all search directories. You can disable this and restore original functionality by passing -disable-searchdir-recurse on the command line.
• #107: Fixes an issue matching operators to existing/old nodes since the C# signature changed recently.
• #98: the fx-bootstrap subcommand now ignores the dependencies folder and does not create an entry in frameworks.xml.
• Improves robustness of loading import files from frameworks.xml ... additionally, it will now report the error (if any) on stdout, and will continue with the update without crashing.

[preview] mdoc v5.0.0.21

This release improves support for UWP/winmd assemblies. It does so by using .NET 4.5 references for BCL types (which are in the metadata as mscorlib, 255.255.255.255, and don't actually exist in the uwp sdk).

[preview] mdoc v5.0.0.20

This release fixes issue #59, by excluding modopt and modreq modifiers from C# signatures.

[preview] mdoc v5.0.0.19

Previously, mdoc simply used the compiler-generated method names in C# signatures for operators, such as op_Multiply, instead of operator *.

This releases fixes that for all unary, binary, comparison, and conversion operators.

Closes #82

[preview] mdoc v5.0.0.18

This release adds support for documenting *.exe and *.winmd files in frameworks mode.

[preview] mdoc v5.0.0.17

You can now include multiple <import> elements for the purposes of importing multiple documentation files, produced by the compiler's /doc parameter.

<?xml version="1.0" encoding="utf-8"?>
<Frameworks>
  <Framework Name="one" Source="one">
    <assemblySearchPath>dependencies/one</assemblySearchPath>
    <import>TestEcmaDocs.xml</import>
  </Framework>
  <Framework Name="two" Source="two">
    <assemblySearchPath>dependencies/two</assemblySearchPath>
    <import>TestEcmaDocs2.xml</import>
    <import>another.xml</import>
  </Framework>
</Frameworks>

[preview] mdoc v5.0.0.15

You can now add a new element to frameworks.xml, /Frameworks/Framework/import, which is a path to the import documentation file. Example:

<?xml version="1.0" encoding="utf-8"?>
<Frameworks>
  <Framework Name="one" Source="one">
    <assemblySearchPath>dependencies/one</assemblySearchPath>
    <import>TestEcmaDocs.xml</import>
  </Framework>
  <Framework Name="two" Source="two">
    <assemblySearchPath>dependencies/two</assemblySearchPath>
    <import>TestEcmaDocs2.xml</import>
  </Framework>
</Frameworks>

Additionally, this release supports a new attribute on the see element, <see href="http://microsoft.com">Microsoft</see> (#62); and also includes a performance improvement in parsing EcmaUrls (05eb484)

[preview] mdoc v5.0.0.14

This release resolves Issue #53 ... forwarded types are no longer skipped.

[preview] mdoc v5.0.0.13

This release is compiled to target Any CPU, and thus will use a larger amount of memory on x64 systems. Resolves #49