#56 vb6 task problems with Auto Increment revision

Tasks (69)
Hani Atassi

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..



  • Hani Atassi

    Hani Atassi - 2004-12-10

    Logged In: YES

    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..

  • Gert Driesen

    Gert Driesen - 2004-12-10

    Logged In: YES

    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

  • Hani Atassi

    Hani Atassi - 2004-12-10

    Logged In: YES

    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.

  • Giscard

    Giscard - 2006-01-16

    Logged In: YES

    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.

  • Dominik Guder

    Dominik Guder - 2011-09-25

    I added "compiledproptery" which defaults to vb6.compiled to nantcontrib 0.91

  • Dominik Guder

    Dominik Guder - 2011-09-25
    • status: open --> closed-fixed

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks