![]() ![]() ![]() For example, initially I had omitted the \Wow6432\ path from my registry value on my updates.txt server side file and this error would surface, once corrected the error went away and the update detection worked as expected. Overwall I belive the issue may be how you have the updates.txt configured, also all settings on the updates.txt file must be valid or you get that error. RegistryKey = HKLM\Software\Wow6432\YOVA\MLMS\Version RegistryKey) Adding unessary values yields weird behavior. I updated my updates.txt by removing property values that did not apply to the configuration such as File Path and adding those mentioned in the documentation (e.g. ![]() We want to be able to uninstall A during install of the comprehensive application B. ![]() Its installer is built with Advanced Installer. Now I have included it in another comprehensive application, B. This actually worked better since my build server increments the version on every release. Its installer is built in a Visual Studio setup project. My solution was to use the Configuration with Version Given by a Registry Value method. When end users would trigger Check for updates on the client side - it would always assume an update was available and if you went through the update/repair process at the end they would get the error mentioned in this question. I experience this issue when I would want to determine if an update was available based on Configuration with File Size Check my updates.txt file on the server side resembled this aiu ĭescription = This update fixes issues related to ticket #999įeature = Added comments section to Chemical ProcessįilePath = c:\Program Files (x86)\YOVA\MLMS\MLMS.exe ![]()
0 Comments
Leave a Reply. |