Hi slages,
to diagnose those problems you can do the following:
Are you seeing the "global macro entry" icon in the main/ribbon toolbar after loading a project? (the {} icon with the "play" overlay) If yes, the last entry is an Plugin info screen which may display an error message why the plugin was not loaded or activated.
If you don't see it here you should take a look in the
PluginApi.log file in
%appdata%\nevigo\articy\3.x\Logs folder.
This should look something like this:
- Code: Select all
[T]: Scanning plugin-folder 'C:\Users\peter\AppData\Roaming\Nevigo\Articy\3.x\Plugins\Local\'
[I]: Collecting versions of plugin 'Articy.ApplyColors' in folder 'C:\Users\peter\AppData\Roaming\Nevigo\Articy\3.x\Plugins\Local\Articy.ApplyColors'
[T]: Manifest 'C:\Users\peter\AppData\Roaming\Nevigo\Articy\3.x\Plugins\Local\Articy.ApplyColors\1.0\x64/PluginManifest.xml' not found.
[I]: Loading API plugin assembly: C:\Users\peter\AppData\Roaming\Nevigo\Articy\3.x\Plugins\Local\Articy.ApplyColors\1.0\AnyCPU\Articy.ApplyColors.dll
[T]: Loading plugin texts from 'C:\Users\peter\AppData\Roaming\Nevigo\Articy\3.x\Plugins\Local\Articy.ApplyColors\1.0\AnyCPU\PluginTexts.tpk'
[I]: Plugin 'Articy.ApplyColors' successfully loaded and initialized
The first "not found" is OK for Plugins that are are "AnyCPU" types.
I just have uploaded a sample plugin in two forms.
1. As installer version that installs to the profile folder (The signed "Release" version with name "Articy.ApplyColors")
2. The source code of that plugin with renamed name (-spaces) MdkSample.ApplyColors. This source is free for anyone to modify, and therefore uses that slightly other name.
The source code still needs some more comments and the texts need to be localized.
To use the source: just unzip, open the solution, add the nuget package and compile.
Hope that helps