There are a few gotchas regarding NDoc on Compact Framework code when you
use code that is specific to the Compact Framework Microsoft.WindowsCE.*
for example and also when inheriting classes where there are naming
conflicts between methods/properties you add and those available only on the
full desktop framework - this is because NDoc reflects your classes from the
full framework, this is a problem when inheriting from CommonDialog and
other classes which are significantly slimmed down on the Compact Framework.
The only workaround is to use conditional compilation and hide sections of
your source code from NDoc by building a documentation specific version of
the app or dll.
Peter
--
Peter Foot
Windows Embedded MVP
OpenNETCF.org Senior Advisor
www.inthehand.com |
www.opennetcf.org
"Felipe T." <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Thx Peter,
>
> Iv tryed NDoc, it works perfectly for DLLs. But i cant get it working on
> EXEs.
> Anyway, ill keep on trying some other tools.
>
>
>
> "Peter Foot [MVP]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > NDoc is a very flexible tool for generating documentation in either CHM
or
> > HTML Help 2.0 format (for integration with the Visual Studio
collection).
> I
> > wrote an article on this a while back
> >
>
(
http://www.opennetcf.org/PermaLink.a...72-bdb2-fe6343
> > 284dca), we use NDoc with all our libraries - you can see the results
here
> > www.opennetcf.org/library/
> >
> >
> >
> > Peter
> >
> > --
> > Peter Foot
> > Windows Embedded MVP
> > OpenNETCF.org Senior Advisor
> > www.inthehand.com | www.opennetcf.org
> >
> > "Felipe T." <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > Hi,
> > > Im wondering what are the tools available for
> > > generating .chm, help and documentation of a .Net project?
> > >
> > > Thx,
> > > Felipe
> > >
> > >
> >
> >
>
>
Similar Threads
