Bugs item #1081472, was opened at 2004-12-08 17:56 Message generated for change (Comment added) made by dogu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=1081472&group_id=54790
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Tasks Group: 0.85 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Hani Atassi (haniatassi) Assigned to: Nobody/Anonymous (nobody) Summary: vb6 task problems with Auto Increment revision Initial Comment: If the VB6 project set to "Auto Increment" the revision number of the version, the task <vb6> compiles the project each time even if it's up-to-date. This is because VB actually update the revision number after it builds the output file. So, the VB project file is always newer.. I fixed this temprorary by touching each output file that the compiler generates after a successful build. I am not sure if there is a better fix.. Thanks, ---------------------------------------------------------------------- Comment By: Dominik Guder (dogu) Date: 2011-09-25 21:14 Message: I added "compiledproptery" which defaults to vb6.compiled to nantcontrib 0.91 ---------------------------------------------------------------------- Comment By: Giscard (giscard) Date: 2006-01-16 04:27 Message: Logged In: YES user_id=1428237 I had the same problem. I solved it similarly, except I edited the code for the vb6 task so that it updates the timestamps of the files it builds after the .vbp get's updated with the new version number. This way you don't have to remember to add a call to touch in the nant scripts, and it doesn't break anything in the case where you aren't using auto-increment. ---------------------------------------------------------------------- Comment By: Hani Atassi (haniatassi) Date: 2004-12-10 18:17 Message: Logged In: YES user_id=590187 Yes Gert, I think it's very important to extend uptodate to use project and solution files, so it would tell us if they are uptodate or not. But still this won't fix the VB problem, because VB touches the project file after a succefull build if "Auto Increment" options is set. Uptodate could be useful in case of manuallly increasing the build number in VB project, but not when Auto Increment option is turend on. ---------------------------------------------------------------------- Comment By: Gert Driesen (drieseng) Date: 2004-12-10 17:38 Message: Logged In: YES user_id=707851 Yeah, we should give it some more thought. I guess we could introduce an interface that tasks that support a "needscompiling" mechanism could implement. We could then extend the <uptodate> to work with these tasks. I'm just thinking out loud here (after having a few glasses of wine), so it might not make much sense ---------------------------------------------------------------------- Comment By: Hani Atassi (haniatassi) Date: 2004-12-10 17:22 Message: Logged In: YES user_id=590187 Another solution would be to set a property to true if the vb project was compiled.. Something like this would be added after a call to ExecuteTask(): Project.Properties["vb6.compiled"] = "true"; and set the same property to false before NeedsCompiling(). In this case i can test for vb6.compiled in my NAnt script and touch the outfile if necessary.. I wonder if this could be a benifit to add to other NAnt tasks like the solution task.. It's a good indecator to inform back the script that the solution was compiled or wasn't because it was uptodate.. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474851&aid=1081472&group_id=54790 ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ NAntContrib-Developer mailing list NAntContrib-Developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
