Indigo Rose Software
  #1  
Old 03-18-2009
Staggan Staggan is offline
Forum Member
 
Join Date: Apr 2006
Posts: 69
Automating Multiple Builds

Hello.

Is there a way to automate the build process?

We have a piece of software we want to patch from version 3.01 to version 3.26

Inbetween there are 20 versions. A single patch to patch all versions to latest is almost 15Mb, so instead I want to patch from each of the older versions to the latest as a single patch.

I can do this by manually doing a build from 3.01 -> 3.26 then 3.02 to 3.26

Can I automate the process and say build ALL versions as single patches up to the latest version?

Thanks

Martyn Hughes
Reply With Quote
  #2  
Old 03-18-2009
Staggan Staggan is offline
Forum Member
 
Join Date: Apr 2006
Posts: 69
I should add that there are so many versions out there because the product has been live for almost 18 months now, and we have a number of older installers being hosted on other websites outside our control. Those sites still bring in quite a few users and so we cannot afford to drop these.

Thanks
Reply With Quote
  #3  
Old 03-18-2009
jassing's Avatar
jassing jassing is offline
Indigo Rose Customer
 
Join Date: Jan 2001
Location: Anderson Island, WA, USA
Posts: 1,898
The power of visual patch is that you include ALL your released versions into one patch file. Just include all 20 versions; and you release 1 single exe as a patch to your current version.
__________________
Reply With Quote
  #4  
Old 03-19-2009
Staggan Staggan is offline
Forum Member
 
Join Date: Apr 2006
Posts: 69
Hello Jassing.

We do that already, but it means that a patch from an almost new version of the game to the latest can be 15Mb because it includes patches for ALL previous versions. Doing this our way, that same patch could be 1Mb instead.

This has implications in two important areas, speed of download for the end user and bandwidth savings for us.

We can do it with two patches, one for those below version XX and one for those above version XX, and this can reduce our patch size to around 5Mb, but using what I am suggesting here we can reduce that even more.

I can achieve what I want manually, I just thought there may be a way to do this automatically.

Thanks

Martyn
Reply With Quote
  #5  
Old 03-19-2009
jassing's Avatar
jassing jassing is offline
Indigo Rose Customer
 
Join Date: Jan 2001
Location: Anderson Island, WA, USA
Posts: 1,898
From the help file....

Unattended Build Options
The following command line options are supported by Visual Patch's design environment for an unattended build process:

Note: The unattended build returns 0 as a process return code if successful, or non-zero if not. You can use this return code to make your batch files respond to the success or failure of the Visual Patch build process.

/BUILD
Tells Visual Patch to build the project file passed in on the cmd line or from a batch file. For example:
"C:\Program Files\Visual Patch 3.0\Visual Patch.exe" /BUILD "C:\TestProj.vp2"

/CONFIG:<<ConfigName>>
Specifies the build configuration to use in the build. If not specified, the first build configuration found in the project is used. For example:

"C:\Program Files\Visual Patch 3.0\Visual Patch.exe" /BUILD "C:\TestProj.vp2" "/CONFIGebugConfig"

/LOG:<<log file path>>
Specifies the location of a log file to output the build status to. If the file exists, it will be overwritten. If the file does not exist, it will be created. For example:

"C:\Program Files\Visual Patch 3.0\Visual Patch.exe" /BUILD "C:\TestProj.vp2" "/LOG:C:\output\Log.txt"

If no log file path is specified, it will be created by default in the output directory.

/STDOUT
Makes the build status go to the standard output device (console). For example:

"C:\Program Files\Visual Patch 3.0\Visual Patch.exe" /BUILD "C:\TestProj.vp2" "/STDOUT"

/CONST:<<ini file path>>
Lets you specify an INI file that contains design-time constants to override the ones in the project. You can define as many design-time constants as you want in the INI file, with each constant on a separate line beneath the [Constants] section. Each constant that is defined in the INI file must already be defined in the project file. For example:



[Constants]
#OUTPUTDIR#=C:\Output\Foobar 2002\Release
#PATCHNAME#=foobar2002patch.exe
#BUILD#=release

When you use the /CONST option along with /BUILD, the specified project file is loaded into Visual Patch, the constants described in the specified unattended-build INI file are set, and the patch executable is generated-all without any interaction.



For example:
"C:\Program Files\Visual Patch 3.0\Visual Patch.exe" /BUILD "C:\TestProj.vp2" "/CONST:C:\MyProj\Config.ini"
__________________
Reply With Quote
  #6  
Old 03-25-2009
Staggan Staggan is offline
Forum Member
 
Join Date: Apr 2006
Posts: 69
Thanks.

Got it working now, and works just as we needed
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Multiple targets? clintsinger MSI Factory 2.0 Discussion 1 08-29-2007 09:25 AM
Playing Multiple Video Files in Sequence Desmond AutoPlay Media Studio 5.0 Examples 0 09-26-2003 12:10 PM
Spanning Content Across Multiple CD's Desmond AutoPlay Media Studio 5.0 Examples 0 09-22-2003 04:38 PM
HOWTO: Make an Install that Spans Multiple CD-ROMs Support Setup Factory 6.0 Knowledge Base 0 10-11-2002 04:36 PM
Default text in edit field - Multiple edit screen Romahe Setup Factory 6.0 1 12-18-2001 02:01 PM


All times are GMT -6. The time now is 09:13 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Copyright © 2000 - 2009 Indigo Rose Corporation. All rights reserved.
Indigo Rose Software