1. Generate documentation only in release mode, build debug mode on development machines
2. Use one of the XML tasks with a foreach to "poke" the documentation setting into the project files before the <solution> task runs.
I think we would all prefer to keep the <solution> task free of custom parameter-forcing flags. There have been a couple of generic parameter-forcing ideas tossed around, but none so far have been clean enough to implement. I can see the use in forcing flags on the build server only, but since the logic in the <solution> task is so complex already, we need a clean way to pass these flags around internally.
[EMAIL PROTECTED] wrote:
Hi,
i'm planning to enable publication of the latest ndoc documentation of my project on the integration website.
One of the requirements before setting up the build process was that it has to be totally seamless for the developer, who actually only uses vs.net and a couple of add-ins (including mailframe testrunner), without having to invoke nant himself. This point is very well achieved through the Solution task.
To follow this requirement for ndoc, I'd like to force documentation generation (only on the build server) without requiring any change on the developer side (especially, without depending on the developer enabling documentation generation in the project, ideally the documentation must not be generated on the developer workstation at all to avoid slowing the build for developers).
This could be achieved through a "forceDocumentationGeneration" boolean attribute on the Solution task, which would then automatically (regardless of the documentation generation settings of its projects) generate the xml files.
Would such a feature be interesting to other people than me ? Or am I missing something and there's already a way to achieve this with similar seamlessness
(I don't wan't to use the csc task itself even if it would allow me to generate the .xml files, but I wish to keep on relying on the Solution task which is working so fine for me)
I made my way through the code and it seems that a few patches to ConfigurationSettings.cs and SolutionTask.cs could do the job (I can contribute on this).
Best regards,
Thibaut Barrère
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg297
begin:vcard fn:Matthew Mastracci n:Mastracci;Matthew org:aclaro Softworks, inc. adr:;;1900 a - 11 St. SE;Calgary;Alberta;T2H 3G2;Canada email;internet:[EMAIL PROTECTED] title:Software Developer tel;work:(403) 299-6612 x-mozilla-html:FALSE url:http://www.aclaro.com version:2.1 end:vcard
