B
bthubbard
This may not be the best group in which to post this. If there is a
better location please direct me there.
I have been experimenting with Sandcastle to generate CHM help file
documentation for some of our projects. I can configure a project(s)
to generate the required XML Documentation file by editing the project
properties via VS or I believe, if we were using one, a XML
configuration file for MSBuild. We usually build our solutions via a
script with a call to MSBuild. I'm wondering if there is a way to
write a command line argument for MSBuild that will instruct it to
generate the XML Documentation file with the same name and target as
editing the project in VS would generate? For example I can add the
property ">MSBuild ... /pocumentationFile=fileName.xml.." which will
generate "fileName.xml". I would rather it generate
"MyNamespace.MyAssembly.xml" in the bin\debug directory for example.
Thanks.
better location please direct me there.
I have been experimenting with Sandcastle to generate CHM help file
documentation for some of our projects. I can configure a project(s)
to generate the required XML Documentation file by editing the project
properties via VS or I believe, if we were using one, a XML
configuration file for MSBuild. We usually build our solutions via a
script with a call to MSBuild. I'm wondering if there is a way to
write a command line argument for MSBuild that will instruct it to
generate the XML Documentation file with the same name and target as
editing the project in VS would generate? For example I can add the
property ">MSBuild ... /pocumentationFile=fileName.xml.." which will
generate "fileName.xml". I would rather it generate
"MyNamespace.MyAssembly.xml" in the bin\debug directory for example.
Thanks.