Hi Stu,
1. The Installer I am handling already have a .NET class performing many other tasks.
This interface between the NSIS installer and the class is already "live a kicking" for a long time ans adding the FindProcess functionality was smooth.
The .NET limitation is not an issue as the installed product nneds .NET runtime and it is pre-requisite for the setup any how.
2. Before using this type of implementation - I briefly looked at the WMI plugin and didn't find processes related functionality. Adding the fact you said before:
Quote:
|
You have to use something like WMI instead (there is a plug-in for this).
|
I assumed that this plugin does not support that.
Am I wrong?
Tx
Oren