For any SLP protected assembly to run on a machine you must install the Runtime components on that machine, using the process outlined in the KB article (http://support.inishtech.com/KB7) referenced in the earlier post.
[The reason the protection/licensing works on your dev machine (and not on other machines) is that the correct runtime components are already correctly installed if Code Protector is installed on the dev machine.]
Depending on your installation preferences, there are several options for invoking the custom installer class,one of which is to use Visual Studio Deployment/Setup Project.
If you wish to take that option, then, while the KB does not call this out explicitly, the first step is to add a Deployment or Setup Project to your solution. To do this, add a new project to the solution and choose the Setup Project template.
Once added, the setup project opens in File System view. Select the Application Folder, right-click in the right-hand side pane and choose Add Project Output.
Then Select Primary Output for your application project (that contains the installer class) which will add the exe or dll file to the installation folder.
To add the Custom Action to the installer, make sure the setup project is selected in Solution Explorer and select the Custom Actions Editor from the Explorer toolbar.
Then to add the custom action to the Install step, in the Custom Actions view select the Install directory, right click and select Add Custom Action, and then select the Project Output from the Application folder.
Then just build the setup project to get your MSI, which you then run on your target test machine.
--John