Discussion:
Generated XML documentation file
(too old to reply)
Jeff Walker
2007-08-28 13:54:05 UTC
Permalink
We have classes defined as follows.

Assembly Name: Root Namespace:
Carpenter.Components.MeltType Carpenter.Components

When the class is compiled, the following is generated
Carpenter.Components.MeltType.dll
Carpenter.Components.xml (Should be Carpenter.Components.MeltType.xml)

We are using VisualBuild to automate the build process and we are attempting
to produce all dlls to a release folder. The problem is when the next class
is built, it over writes the shortened xml file.

This works
Assembly Name: Root Namespace:
Carpenter_Components_MeltType Carpenter.Components

When the class is compiled, the following is generated
Carpenter_Components_MeltType.dll
Carpenter_Components_MeltType.xml

We prefer the . structure since it is more intuitive with the namespaces. I
was able to use a post build event to rename the file, but was hoping for a
better solution.

Thanks
--
Jeff
Stevanich
2007-09-01 18:31:00 UTC
Permalink
Jeff,

The XML documentation files are generated one per assembly, based on the
assembly's file name by default. You can change the XML documentation file
name manually in the *.*proj file.

In each configuration property group can be found:

<DocumentationFile>TestProject1.xml</DocumentationFile>

Hope this helps,

Steve - dotneticated.com
Post by Jeff Walker
We have classes defined as follows.
Carpenter.Components.MeltType Carpenter.Components
When the class is compiled, the following is generated
Carpenter.Components.MeltType.dll
Carpenter.Components.xml (Should be Carpenter.Components.MeltType.xml)
We are using VisualBuild to automate the build process and we are attempting
to produce all dlls to a release folder. The problem is when the next class
is built, it over writes the shortened xml file.
This works
Carpenter_Components_MeltType Carpenter.Components
When the class is compiled, the following is generated
Carpenter_Components_MeltType.dll
Carpenter_Components_MeltType.xml
We prefer the . structure since it is more intuitive with the namespaces.
I
was able to use a post build event to rename the file, but was hoping for a
better solution.
Thanks
--
Jeff
Loading...