> One of my favorite reasons for leaving NUnit code in a different assembly
> than the code to be tested... If you had, you could simply exclude the
> assembly from ndoc's consideration.
Another option, if you do as I and put your NUnit tests in the same
assembly. I don't want my NUnit tests in my release code, so my NUnit
classes are wrapped inside #if DEBUG/#endif directives. I run NDoc
against my release build.

Signature
Tom Porterfield
Finn J Johnsen - 04 Oct 2004 14:31 GMT
Thanks for good suggestions. However I found a way that will work for
now : SkipNamespacesWithoutSummaries in the ndoc setting. This forces me
to write summary for every namespace I want included in my doc's. And to
seperate testclasses in dedicated test - namespaces. I do this simply by
adding .Test to my testclasses namespace.
However I might go for the #if DEBUG/#endif in the future, so I don't
have to deploy with the nunit assemblies.
Thanks,
Finn Johnsen