How to update Marvin Beans?

A user wrote:

Can you confirm if the only way to update the software is a complete re-install
Also can you please confirm if it’s necessary for us to perform this update so often ?

We recommend to use the installer that uninstall the previous version
and setup the new one. It is the most comfortable way to maintain the
coherency of the package.


But under Linux and Mac systems, manual update (overwrite files in
current MarvinBeans directory from the new patch) can be enough.



If you use Windows, update without installer can be unconfortable.

Windows installer registers marvinOLEServer.exe and native libraries.
If you do not use the installer, you have to do it manually.

Furthermore, installer updates settings in batch files in the bin
folder of Marvin. If you overwrite batch files, you have to restore
these settings.



To update Marvin without installer, follow these instructions (you need admin privileges):

• 
  Close all Marvin applications and running Office applications (opened
  Office document can contain embedded Marvin objects).


• 
  Unregister current Marvin dll-s: run unregistercxn.bat in the
  lib\EMFExport folder of the MarvinBeans directory (since 5.3).


• Unregister current Marvin OLE server: run uninstallole.bat from the
  MarvinBeans directory.


• Overwrite files in the MarvinBeans directory from the new MarvinBeans
  patch release (marvinbeans-VERSION.zip).


• Register Marvin OLE server: run installole.bat from the MarvinBeans
  directory.


• 
  Register updated version of Marvin dll-s: run registercxn.bat from
  the lib\EMFExport folder of the MarvinBeans directory (since 5.3).


•  In the bin folder of the MarvinBeans directory run the config.bat
  script to restore settings in the batch files.

By the way, you can run installer/uninstaller in silent (unattended)
mode, just give the -q option in command line. E.g.:

marvinbeans-5_3_0_2.exe -q

 In earlier Marvin versions, update in silent mode was buggy (if Marvin
was already installed, silent mode installation failed) but this
problem has been fixed in 5.3.x series.