WhisperingTreeWhisperingTreeMy previous post was based on the assumption that the v3.2.5 beta download was an installer instead of a replacement for Podium.exe in a v3.2.4 installation. I now have Podium_325_x64_beta5.exe in the same folder as Podium.exe. I also now have Microsoft Visual C++ 2015 Redistributable Update 2 x64 installed.
I am still learning v3.2.4, so often I don’t know whether a problem is due to my lack of experience with Podium versus a Podium bug. When I find a problem, I would like to try v3.2.5 to see if it is a bug already fixed. I could solely use v3.2.5 beta instead, but I understand it is not fully tested and could have bugs not in v3.2.4. So I see the need to go back and forth between v3.2.4 and v3.2.5 beta.
Which files are NOT compatible between v3.2.4 and v3.2.5 beta? For example, Podium.ini, PluginDatabase_x64.pod and project files (.pod)?
WhisperingTreeAfter I purchased Podium, I first attempted to install v3.2.5 Beta5 x64 on my Win8.1 x64 PC. It didn’t install anything, such as programs under C:\Program Files\, and threw no error messages. Therefore, I installed v3.2.4 x64, and it has been working fine.
Perhaps the problem is that I have neither the Microsoft Visual C++ 2015 Redistributable nor the KB2999226 Universal C Runtime installed before installing v3.2.5 Beta5. I found update 2, which includes both, here: https://www.microsoft.com/en-us/download/details.aspx?id=51682
Including the redistributable in the v3.2.5 installer may not be the best solution. When the user installs v3.2.5, a newer update with bug and security fixes may be available. Also, if Podium v3.2.5 x86 installs the x86 redistributable, a user with x64 Windows will need to install the x64 redistributable later when an x64 program is installed. Better for the x64 Windows user to only install the x64 redistributable, which supports both x64 and x86 programs.
My first suggestion is to put a link the latest update of the Microsoft Visual C++ 2015 Redistributable on the Podium downloads page with note saying that it is a requirement for v3.2.5. My second suggestion is to throw an error dialog in the v3.2.5 installer if the redistributable or KB2999226 is not installed.