Tim,
The doc files are being generated by the NAnt script. In the
nant-common.xml file, the following csc task line is used:
<csc if="${current.build.keysign}" keyfile="${snk.file}"
> target="library"
> define="${current.build.defines}" warnaserror="false"
> debug="${csc.debug}" optimize="${csc.optimize}"
> output="${build.bin.dir}/${project.name}.dll" *
> doc="${build.bin.dir}/${project.name}.xml"*>
>
I have updated the package.ps1 scripts files in the trunk and the 1.2.x
branch to start including these files when the ZIP files are created.
In the meantime, what would be an easy way to release the XML files for
those that want them?
On Fri, Feb 12, 2010 at 11:10 AM, Timothy Bish <tabish...@gmail.com> wrote:
> On Fri, 2010-02-12 at 11:04 -0800, magellings wrote:
> > Tim can you include the .xml intellisense files with the binaries? These
> > provide good user experience when developing against the referenced NMS
> > framework classes.
> >
> > Right click project > Properties > Build > check "XML documentation
> file".
> >
> > Then when you include the xml file in the same folder as the dll you can
> see
> > all the xml comments done on the NMS classes.
> >
> > -Thanks
> >
>
> They only way this would get included was if there was some automated
> way to generate them from nant as I don't use Visual Studio to build or
> test the project, everything is done via command line so it can be done
> via automation.
>
> If you have some way to do this that we could include into the nant
> scripts and packaging script we'd welcome the patch.
>
> Regards
>
> --
> Tim Bish
>
> Open Source Integration: http://fusesource.com
> ActiveMQ in Action: http://www.manning.com/snyder/
>
> Follow me on Twitter: http://twitter.com/tabish121
> My Blog: http://timbish.blogspot.com/
>
>
