Archive: How does NSIS framework handles...


How does NSIS framework handles...
I'm still learning about NSIS and I’m wondering
how does NSIS framework handles the situation where I register a DLL (just self-register) but an application needs to be shut down.

For example, specifically I need to register Redemption.dll which is used by our software to do some stuff with Outlook. If Outlook is opened, then NSIS throws an error:

***************
"Error opening file for writing: "c:\filepath\Redemption.dll"
Click Abort to stop the installation, Retiry to try again, or Ignore to skip this file. Clicking retry or ignore and the installation continues...
***************

I've seen other installation frameworks where they'd prompt user the close the application i.e. in this case the user will get a prompt that the Outlook needs to be closed (for the Redemption to be registered).

So i'm not sure how does NSIS framework handles this particular case? It seems right now that i have to add logic to detect if outlook is running and prompt user to close it before launching installation of our software. Please advice if there’s an alternative and it’ll be great if someone can just explain how NSIS handles this case. Thanks!


Re: How does NSIS framework handles...

Originally posted by zanz
It seems right now that i have to add logic to detect if outlook is running and prompt user to close it before launching installation of our software.
That's exactly right ;)

However there are plugins that might help you there :)

This one might be helpful:
http://nsis.sourceforge.net/LockedList_plug-in

Thanks for help!