Call .NET DLL methods plug-in

Author: claesabrandt (talk, contrib)

NSIS forum thread

Description

This is a NSIS plug-in, that can call methods in your managed .NET DLL.

Place the plugin in the NSIS plugins folder. You call your .NET DLL methods by calling CLR:Call. This expects the following parameters:

• Assembly dll filename
• Namespace and classname with dot in between
• Method name
• Number of parameters
• Parameters

At the moment, the supported parameter types are string, char, int, float and boolean. Return value can be of those types too but are returned as strings to NSIS. Before calling the plug-in, call SetOutPath and copy the .NET DLL to be invoked. Note that the .NET class must be marked as public.

Sample NSIS script calling a method in a .NET DLL, which takes five parameters: string, char, int, float and boolean and returns a string:

InitPluginsDir
SetOutPath $PLUGINSDIR
File "SomeAssembly.dll"
 
CLR::Call /NOUNLOAD "SomeAssembly.dll" "SomeNamespace.SomeClass" \
  "SomeMethod" 5 "mystring1" "x" 10 15.8 false
CLR::Destroy

pop $0  
MessageBox MB_OK $0

Notice the /NOUNLOAD. This is nessecary if you need to call CLR::Call more than once, otherwise the installer hangs on the second call. When done with calling CLR::Call, call CLR::Destroy.

You do not have to put quotes around the dll filename, namespace, classname and method, but if the dll filename contains spaces, you need the quotes around that. Omitting the quotes only makes the code slightly easier to read, the result is the same.

The plug-in is fully functional but still undergoes some development and changes.

Download

Version 0.5 including source is available here CLR.zip (35 KB) as-is.

Prerequisites

The plugin will need the .NET 2.0 framework to be installed on the target machine. It can be included in the installer or downloaded using for instance the inetc plugin.

Issues

When the installer finishes, the CLR.dll file remains in the temporary plugins directory on the target machine. The file is not locked, but somehow the plugin cannot be deleted. The next time the user reboots the machine, this file is deleted automatically. This issue is being worked on.

Version history

• 0.1 Initial release of the plugin
• 0.2 Changed to native NSIS plugin and some bugfixes
• 0.3 Bugfix: If more than one class was found in an assembly, only the first one could be loaded.
• 0.4 CLR.dll is now compiled in release mode, in order to work on systems without VS2008 installed. Various other minor bugfixes as well.
• 0.5 CLR.dll is now compiled with Visual Studio 2005 so there is no need for Visual C++ 2008 Redist.