As I wrote last time, I recently switched OnTopReplica's installer from ClickOnce to a custom NSIS installer. In doing so I was voluntarily dropping a lot of nice features of ClickOnce (user-level installation, simple interface, automatic updating and Visual Studio integration) for a set of features I had to implement on my own. It worked out surprisingly well, so here's what I've done.
In the last weeks I've received several mails about OnTopReplica, which was apparently crashing for a lot of users. After some tinkering, my installed copy started crashing too for some reason (which is when I decided I had to do something about it 
). What I found out is that the app wasn't crashing, but failed to start for some unknown reason.
Even if I'm still unsure about the exact reason why OnTopReplica would crash, it appeared to be related to ClickOnce and the way the app is launched. So I decided to ditch ClickOnce (which is unfortunate, since it did work pretty well until now and I liked the auto-updating feature).
Anyhow, if you install OnTopReplica now you will get a custom NSIS installer instead of the ClickOnce .application file. I still tried to keep the installer as noninvasive as possible: user elevation is not required!
The installer will only write to the current user's registry and extract the executable to the local application data folder (i.e. C:\Users\User\AppData\Local\OnTopReplica), exactly like Google Chrome. Automatic updating must yet be implemented, but the app will notify you if updates are available.
If you installed OnTopReplica via ClickOnce, please uninstall it and reinstall the new version. Sorry about the inconvenience (but as a bonus: the new version includes a fix for a memory leak... so, there you go 
).
descending
