Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Versioning of RBuilder Runtime Packages (*.bpl)

edited September 2001 in General
Any chance you will start versioning your runtime package files making sure
to increment them with each and every maintenance release?

We are thinking of using RBuilder in our application which is Webbrowser
based. All of our client forms are Activeforms. So all required files are
automatically downloaded to the client based on the Module Version. Whether
is is a .dll, .ocx, .exe, .bpl etc. Without versioning auto-updating
doesn't work.

Thanks, Dave.

Comments

  • edited September 2001
    We're going to look into adding build version numbers. Can't promise we'll
    have it in the next release, but it has been requested before, and it
    appears that it certainly would be helpful to start adding them. Thanks for
    the feedback.


    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited September 2001
    If we buy the Professional version which comes with source, do we have
    everything necessary to re-compile the runtime packages with versioning in
    the interim? If so, does this go against your licensing? The reason I ask
    is because we REALLY need a new report writer. I have looked at yours as
    well as Rave. Report Builder is definitely the way to go but we need the
    runtime packages versioned.

    Thanks, Dave.


  • edited September 2001
    Yes, with RB professional, you have all the source necessary to rebuild RB's
    packages, and you can add the version information. FYI, RB Enterprise has
    RAP, and this is the only source we do not provide.


    Cheers,

    Jim Bennett
    Digital Metaphors


This discussion has been closed.