Stop moving of helper applications when migrating BOINC Data directory

[Ageless]

Something that came up through the Seti forums, ​this post from archae86 moving from 5.10.45 to 6.6.20

7. For better or worse, on this host I had several third-party BOINC "helper" aps installed under the /program files/BOINC directory, including BOINCView, BoingLogX, and a couple of others. After the 6.6.20 install, I found that it had moved them to the new BOINC data directory under \Documents and Settings\All Users\Application data. Of course this was incompatible with their launch conditions, so I moved them back manually.

Perhaps it is possible to check for these programs and either warn the user to uninstall them before allowing the migration to continue, or for the installer/migration program to leave them be in the BOINC directory?

[Nicolas]

Such tools have no business being in C:\Program files\BOINC. They should be in their own directories.

[Ageless]

Some of them don't work in their own directories as then they can't find the client_state.xml file. it wouldn't be a problem if you just unzip the programs into the BOINC or BOINC Data directory (depending on version of BOINC), but it becomes a whole different kettle of fish when these programs use an installer.

[romw]

I imagine these helper applications assume that the client_state.xml file or gui_rpc_auth.cfg file are going to be in the directory it is launched from.

If we don't move the executable it'll fail to function properly anyway.

Incompatible with their launch conditions means to me that the shortcuts failed to find the executable.

If a third party application knows how to find the data directory, it really should be installed to its own directory.

[Nicolas]

And apps reading client_state.xml deserve what they get; the GUI RPCs are there for a reason.