I like the wrapper idea. I never understood why NAnt included NDoc instead of just spawning it. Same thing applies to NUnit.
 
It would be cool to have a common way of detecting the packages locations. I think we can use pkgconfig approach on Unix and AssemblyFolders or other registry place on Windows (all we need to do is to convince the developers to provide the appropriate registration procedures or prepare them ourselves).
 
NAnt would then be able to provide a common way to get the paths:
 
package::installed('NUnit2') - true/false
package::get-version('NUnit2') - 2.2.0
package::get-lib-path('NUnit2') - "C:\Program Files\NUnit 2.2\bin"
package::get-exe-path('NUnit2') - "C:\Program Files\NUnit 2.2\bin"
 
Of course, much more needs to be done to properly use versioning and framework support but that's the idea.
 
Jarek
 
----- Original Message -----
Sent: Sunday, December 19, 2004 1:40 PM
Subject: RE: NDoc 1.3

Hi Jarek,
 
I'm still in flux on how to proceed with this. Adding all documenters (and their dependencies, which at this time is only the Interop.MSHelpCompiler.dll assembly) to the NAnt distribution would increase the size of the NAnt distribution quite a lot (as we have to include them for each support target framework).
 
If we do not include all documenters, then we should at least provide more information to our users on how to make the other documenters that available for usage by the <ndoc> task.
 
In the end, it would've been better if we could convert the <ndoc> task to a wrapper for NDocConsole, but then we'd need to have some mechanism on both Windows and Linux to discover the install directory of NDoc.
 
Gert
 

From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]
Sent: zondag 19 december 2004 12:34
To: Gert Driesen
Subject: NDoc 1.3

Hi Gert!
 
Will NDoc.Documenter.Xml.dll and other documenters be included in NAnt 0.85 ? Currently only NAnt and MSDN documenters are available to <ndoc> task.
 
Jarek

Reply via email to