|
#2
|
|||
|
|||
|
How to archive TU update in source control system
Brett,
I would like to save each TU update separately in our source code control environment. This is so that we can keep careful control over the version of software we are using and can revert if necessary. If I save the 2.0.1.0 patch exe, will it apply itself automatically upon execution, or does it require a special calling convention? For example, I notice the following file and the use of irpatch.exe seems to be involved: [Common] FileArc=C:\Program Files\TrueUpdate 2.0\Downloads\tu20patch-2.0.1.0.exe Offset=279143 Thanks for any explanation about how to manually apply the 2.0.1 patch at some later date. Ken Gartner |
|
#3
|
||||
|
||||
|
As long as the 2.0.0.0 version is installed properly, the 2.0.1.0 patch will always work via a simple double-click.
|
|
#4
|
||||
|
||||
|
Ken Gartner,
You can always open a support ticket here with your serial number and we can send you download instructions to the full file. This way you can have a stand alone setup for each version. Adam Kapilik |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Press Release: TrueUpdate 2.0 | Colin | Announcements & News | 0 | 03-15-2005 12:27 PM |
| TrueUpdate 2.0 FAQ | Colin | TrueUpdate 2.0 | 0 | 01-04-2005 01:25 PM |
| What's New in TrueUpdate 2.0? | Colin | TrueUpdate 2.0 | 0 | 01-04-2005 01:24 PM |
| Key Features of TrueUpdate 2.0 | Colin | TrueUpdate 2.0 | 0 | 01-04-2005 01:23 PM |
| TrueUpdate 1.0 Press Release | Ted | TrueUpdate 1.0 | 0 | 08-17-2001 03:34 PM |
All times are GMT -6. The time now is 04:12 PM.






Linear Mode

