Follow these steps to move your projects to a new ODA BimRv SDK version:

1. Be sure your project can be rebuilt with the existing ODA BimRv SDK version; do a full rebuild. If this does not work, it should be fixed before trying a new ODA BimRv SDK version.
2. Download new ODA BimRv SDK zip files from the Member Download Area (make sure you are logged in).

   There may be multiple configurations even for the same compiler: for example, a static or DLL configuration. Naming conventions for .zip files are described here. The easiest way to detect which configuration is used in your project is to go to the ODA BimRv SDK /exe or /lib folder, which contains sub-folders with the name of the configuration that is used, for example: vc14_amd64dll, vc15_amd64dlldbg, etc.

3. Replace the old ODA BimRv SDK files with the new ones. Be sure to replace all files. A mixture of .lib, obj, .h, or .cpp files of different versions will cause problems which are hard to detect.

   To avoid this, unpack a new version of the archive to an empty folder (not on top of the old version). Because of this, it's not recommended to copy/move files from the /Examples, /Extensions, and other folders to another place. Keep them in the ODA BimRv SDK folder so that they will be updated while moving to a new version.

   Unpacking the Release and Debug archives into the same folder is permitted.

   Different files in the /lib and /exe folders will go into different sub-folders. Some files such as those in /Include and /Examples are duplicated in Release and Debug zip files, but they are actually the same.

4. Change the project settings to use the path to the new ODA BimRv SDK folder.

   Note: Changing not only Include and Lib paths may be required.

   Your project may reference .h and .cpp files from /Examples, /Extensions, and other folders, and these files should be from the correct ODA Platform folder. Using relative paths makes things easier.

   For example:

   Version 21.7
     |___MyProject
     |___ODA_SDK
           |___BimRv
                |___Examples
                |___Extensions
                |___Include
           |___exe
           |___lib
           

   In this case, all paths can be relative and will not require updating after a new ODA BimRv SDK version is unpacked into a new folder and your project is copied.

5. Carefully read the Release Notes to get information about all changes between the version of the BimRv SDK you currently use and the version you are going to use after the upgrade. Make corresponding changes in your code (if it is necessary).
6. Do a full rebuild of your project. Be sure the project builds successfully.