How to upgrade
From VbGORE Visual Basic Online RPG Engine
This guide will teach you everything you need to know about how to upgrade between versions of vbGORE.
Starting out
The first step to upgrading is finding out what version of vbGORE you have. This can be found by the large commented license in the server or client Declares module. It is important that you use the correct versions when upgrading.
Viewing the change log
The change log shows you every important change that has been made between versions. As of version 1.0, this log has been upgraded to more detail, giving you information such as what files were affected by the change, and whether or not they are shown in the upgrade log, which is represented by the (Guide) tag, which will link you to the corresponding upgrade guide.
Not all changes have or will have a guide for upgrading between versions, nor will all the guides be the same. How they work and if they exist is completely dependent on the type of upgrade. Vital upgrades, such as bug, performance and security fixes will most likely have a upgrade guide, while feature additions will not because they are not vital.
You will not need to upgrade everything between versions. If you only upgrade the vital fixes, you will be fine. Choose what you need (often good to start with everything starting with Fix), and only add the rest if you wish to spend the time adding it.
Using the upgrade guide
The upgrade guide is written to be as straight-forward as possible. The title of the guide will state what version it will upgrade to. It is safe to assume that the versions will be taken one at a time - that is, you won't find a guide upgrading through 3 versions at once or skipping any versions.
Always follow the guide from bottom to top!
The guides are written in the same order as the change log, where newest entries are on top. Following from bottom to top allows you to upgrade in the order upgrades are written. If you follow from top to bottom, you may run into references made by other updates, making the upgrading process more difficult.
The upgrade guide lists the upgrades by the same name used in the change log. For example, if you see the following entry in the change log:
Fix - ToolFreeNumber: (Guide) Fixed a small typo in ToolFreeNumber for the Grh finding. Files affected: ToolFreeNumber.frmMain
You know that the name used in the upgrade guide will be Fix - ToolFreeNumber. Clicking on the (Guide) text will lead you directly to this fix in the upgrade guide.
The upgrade guide is written in a open, find and replace format. That is, it will tell you what file to open, what code to find, and what to replace it with. The search function can be found by pressing Ctrl + F in the Visual Basic 6 IDE.