Hi,
I noticed that there was discussion of modifying the uptodate to check
if VB6 projects were up to date before compiling. Also, there was
discussion that the auto-increment means that the project will be
recompiled every time (I get around this using touch on the target).
I have updated (i.e. hacked w/ 10 or so lines of code) the vb6 task
locally to include the following attributes
compile="<boolean>"
uptodate="<property>"
(NAnt has a nice object design making changes easy, BTW.) This way, the
vb6 task can be run to check if the project is up-to-date without
compiling <or> the project can be compiled and an up-to-date property
can be set. (My only reservation is that with these attributes, the vb6
task can do nothing at all!)
It works great.
We have an additional requirement because we are using FailSafe to rig
the code, and we only want to do that if the project has changed. We are
also checking out from VSS (to save the bumped version number) and that
is also unnecessary (and time consuming) if the project is up to date.
Is this something that the user/developer community wants in the code?
I'm working with the 8.5 rc3 baseline currently, but could properly code
from the CVS.
Thanks,
Henry Lafleur | ,__o
Bengal Development | _-\_<,
(337) 991-0083 ext 229 | (*)/'(*)
mailto:[EMAIL PROTECTED]
http://www.bengaldevelopment.com/
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
NAntContrib-Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
