Generate document from XML without assembly?

[jhermsen]

I am looking for a way to generate a document from a xml documentation file without having an assembly.

Is it possible with Sandcastle and if so how?
I tried using the file as document source, but it keeps telling me it requires an assembly or project.

The documentation xml that I have is generated from Microsoft Dynamics Ax code that's why I have no assembly.

Any advice is welcome

[EWSoftware]

No, it has to have the assembly to generate the API info. The XML comments are then merged with that to produce the API documentation. You can produce a help file based on conceptual content alone using the Additional Content Only plug-in but that relies on MAML topics. In theory, a plug-in could perhaps be created that converts the API XML comments to equivalent MAML topics and related content layout file that could then be built.

[jhermsen]

Thank you for you answer.
I don't know that much about the xml documentation and MAML, but I included an example of two xml files that get produced by Ax.

Can you tell me if it's usable and includes the details needed to continue looking into some plugin?

Reflection output:

<?xml version="1.0" encoding="utf-8"?>
<reflection build="5.0.1500.6491" xmlns:msxsl="urn:schemas-microsoft-com:xslt"
    xmlns:ddue="urn:ddue-extensions">
    <apis>
        <api api="R:Project">
            <apidata group="root" pseudo="true" />
            <elements>
                <element api="T:Tutorial_ShowAviFiles" />
            </elements>
        </api>
        <api id="T:Tutorial_ShowAviFiles">
            <apidata name="Tutorial_ShowAviFiles" group="type" subgroup="class" />
            <typedata id="1723" final="false" abstract="false" runon="Client" />
            <family>
                <ancestors>
                    <type api="T:Object" />
                </ancestors>
                <descendents />
            </family>
            <syntax>class Tutorial_ShowAviFiles</syntax>
            <elements>
                <element api="M:Object.notifyAll" />
                <element api="M:Object.usageCount" />
                <element api="M:Object.handle" />
                <element api="M:Tutorial_ShowAviFiles.buildForm" />
                <element api="M:Tutorial_ShowAviFiles::main" />
                <element api="M:Tutorial_ShowAviFiles.scanMacro" />
                <element api="M:Object.cancelTimeOut" />
                <element api="M:Object.equal" />
                <element api="M:Object.new" />
                <element api="M:Object.notify" />
                <element api="M:Object.objectOnServer" />
                <element api="M:Object.owner" />
                <element api="M:Object.setTimeOut" />
                <element api="M:Object.toString" />
                <element api="M:Object.wait" />
                <element api="M:Object.getTimeOutTimerHandle" />
                <element api="M:Object.xml" />
            </elements>
            <containers>
                <type api="R:Project" />
            </containers>
            <file>AxDeveloperDocs.chm::/html/DF0A511D-03B5-439D-8596-BE9E4AEF3462.htm</file>
        </api>
        <api id="M:Tutorial_ShowAviFiles.scanMacro">
            <apidata name="scanMacro" group="member" subgroup="method" />
            <memberdata visibility="public" static="false" abstract="false" runon="Client" />
            <containers>
                <type api="T:Tutorial_ShowAviFiles" />
            </containers>
            <syntax>public void scanMacro()</syntax>
            <file>AxDeveloperDocs.chm::/html/D862C7DE-4419-4814-A31A-EF479440B6DE.htm</file>
        </api>
        <api id="M:Tutorial_ShowAviFiles::main">
            <apidata name="main" group="member" subgroup="method" />
            <memberdata visibility="public" static="true" abstract="false" runon="Client" />
            <parameters>
                <parameter name="_arg" optional="false">
                    <type api="T:Args" />
                </parameter>
            </parameters>
            <containers>
                <type api="T:Tutorial_ShowAviFiles" />
            </containers>
            <syntax>client public static void main(Args _arg)</syntax>
            <file>AxDeveloperDocs.chm::/html/955239ec-1a2d-47dc-bfaa-d93c55d90e27.htm</file>
        </api>
        <api id="M:Tutorial_ShowAviFiles.buildForm">
            <apidata name="buildForm" group="member" subgroup="method" />
            <memberdata visibility="public" static="false" abstract="false" runon="Client" />
            <containers>
                <type api="T:Tutorial_ShowAviFiles" />
            </containers>
            <syntax>public void buildForm()</syntax>
            <file>AxDeveloperDocs.chm::/html/B5E9A8BF-743A-4462-B447-18583EB9ACA5.htm</file>
        </api>
    </apis>
</reflection>

Documentation output:

<?xml version="1.0" encoding="utf-8"?>
<doc build="5.0.1500.6491">
    <members>
        <member name="M:Tutorial_ShowAviFiles::main" automated="true">
            <summary>Provides an entry point for the <c>Tutorial_ShowAviFiles</c> class when it is
                called from a menu item.</summary>
            <param name="_arg">The arguments for the <c>Tutorial_ShowAviFiles</c> class.</param>
            <remarks>Use the <c>main</c> class design pattern whenever a class is called from a menu
                item. Do not call the <c>main</c> method explicitly from the code; call it
                implicitly from a menu item. Typically, you would: <list type="bullet">
                    <item>
                        <description>Instantiate the class by calling the static <c>construct</c>
                method.</description>
                    </item>
                    <item>
                        <description>Call the <c>prompt</c> method to create a dialog box.</description>
                    </item>
                    <item>
                        <description>Call the <c>run</c> method, if the user clicks <ui>OK</ui> in
                the dialog box.</description>
                    </item>
                </list>
            </remarks>
            <seealso cref="Access a Class from a Menu" />
        </member>
    </members>
</doc>

[EWSoftware]

The reflection data file is mostly in the correct format and the XML comments file looks okay. The file elements in the reflection data would need correcting to strip the protocol, path, and extension from the values. It's likely you could create a plug-in that runs in place of the GenerateReflectionInfo build step and copies the reflection data file to the working folder. Likewise, it could handle the validating data source build step to run in place of it and just copy the XML comments file to the working folder and add it to the list of comments files the build engine will use.