How can I create and include a plugin?

Log4View is capable of including user generated plugins. There are visual plugins you may add to the GUI of Log4View and receiver plugins that allow you to receive messages from your own appenders. When installing Log4View, include the Sample Receiver and Sample Dashboard to install code examples of plugins in your Log4View main directory. Your plugins will have access to our powerful API documented at “<Log4ViewDirectory >\Help\Log4ViewAPI.chm”.

Your plugins must follow the name pattern Log4View.*.dll and have to be copied in Log4View’s main directory to be included.

How do I debug a plugin?

There are two ways for debugging your own plugins. The first one is to debug via Visual Studio. Go to “Debug” -> “Attach to Process…” and select Log4View. You should now be able to use the Visual Studio Debugger within the code of your own plugin.

Another way is to send log messages at critical sections of your plugin's code. Log4View already features an integrated a status logger you may call via

LogManager.GetCurrentClassLogger().Info("Example");

This way a message “Example“ with the Loglevel Info will be logged via TCP-, file- or Traceappender, depending on your entries in the Log4View.exe.config (in the main directory of Log4View) in the section of log4net.

To supervise these messages in real time, you can use Log4View again. The easiest way is to copy the whole directory of Log4View and to change the file path of its log file in its Log4View.exe.config (else you would receive the status messages of both the logging and the receiving instance of Log4View). Start the copied Log4View and attach the logging one’s file via a file receiver.