Plugin development

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Plugin development

sinsedrix
Hello,

I do not know how to begin a plugin development so I wonder if there is a sample plugin somewhere.

Thanks
Reply | Threaded
Open this post in threaded view
|

Re: Plugin development

Philipp Lauchner
Administrator
Dear sinsedrix,

a sample plugin is available at the installation path of Log4View in the folder SampleDashboard repectively SampleReceiver. The API documentation is also at the installation path in the Help folder. More information can be found here:
http://www.log4view.com/support/documentation/

Yet our upcoming major release will switch from WinForms to WPF technology, requiring some adjustments to dashboard plugins written for the current version. Thus we advice you to develop your plugin to have its business logic connectable to a new view logic in an easy way.

Yours sincerely

Philipp Lauchner
PROSA GmbH  
Development & Support
Reply | Threaded
Open this post in threaded view
|

Re: Plugin development

sinsedrix
Ok thanks, I can see it now. But there are missing files in the projects :
- Log4View.dll
- app.config
- SampleReceiverKey.snk
Reply | Threaded
Open this post in threaded view
|

Re: Plugin development

Ulrich
Administrator
- You don't need a Log4View.dll, but instead reference "Log4View.exe". (In fact every .exe file is just a .dll plus some additional bootstrapping code.)

- app.config isn't needed, just remove the reference.

- SampleReceiverKey.snk is missing because we cannot provide our private key file. Instead just create your own .snk file and use it. It isn't necessary to use a special .snk file, it's just necessary that your plugin is signed.

Ulrich
Reply | Threaded
Open this post in threaded view
|

Re: Plugin development

sinsedrix
Thanks, I could progress a bit.

Now I have the following error at compilation time :
The type or namespace name '(Message|ICustomControlFactory|Extensibility|CustomControl)' could not be found (are you missing a using directive or an assembly reference?)
However when I reach their definition (F12) from the sample code, I can see these types in the Log4View.dll file (that I copied from Log4View.exe).

Do you have an idea of what is going wrong?
Reply | Threaded
Open this post in threaded view
|

Re: Plugin development

Ulrich
Administrator
You don't have to copy Log4View.exe to Log4View.dll. You can directly reference Log4View.exe.
This could be the reason why the compiler couldn't find the namespace.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin development

sinsedrix
No, I came back to the original name (+ clean, reload, regenerate). I still have the same compilation errors.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin development

Ulrich
Administrator
Ok, I have just checked it by myself.
You are right

You have to reference two additional dlls, both located near Log4View.exe:
- Log4View.Utils.dll
- Log4View.TelemetryInterface.dll

We forgot to update the reference project respectively.
Sorry for this.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin development

sinsedrix
I add these DLL as references of the projects (+ clean, reload, regenerate). I still have the same compilation errors.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin development

Ulrich
Administrator
Does the plugin project use .NET Framework 4.6.1?
Reply | Threaded
Open this post in threaded view
|

Re: Plugin development

sinsedrix
I had the .NET Framework 4.6.1 installed but not the corresponding Developer Pack. Now, it is done and I could properly launch the plugins into Log4View.

Thanks a lot.