Tracing debug/log from addin

[Maxim-CADman77]

I'd like to know the correct way to trace debug/log from my addin.

l've already succeded with tracing in iLogic  (logger.debug...)

...and in plugin version (Debug.WriteLine ...+DebugView++ filter set to plugin's exe process).

I expected addin would behave like plugin (just set filter to inventor.exe) but there is nothing there...

[Maxim-CADman77 · Accepted solution]

On my config Debug.WriteLine works as expected only if DebugView++ was started with "Run as administrator".

[Michael.Navara]

There is no standard way to logging from add-in. iLogic has it's own logging system and plugin uses Debug.WriteLine method and somehow handles the listeners.

I usually use third party logging system log4net. It is very powerful and flexible system.

[Maxim-CADman77]

@Michael.Navara 

What is the key feature of log4net in context of log from Inventor add-in.
It can filter out the given add-in only output from the complete inventor.exe output?

[Michael.Navara]

Key features for me are:

• I can select from many Appenders. Because my applications (like product configurators) works in different environments (desktop Inventor, JobServer, Forge Design Automation) and share one code base (single bussines logic for all), I need to change logging behavior for each deployment.
• When I need to analyze some issues, I can configure different logging level for each class or command. Usually I set logging level to warning and above, but for some classes I can set verbose logging to different target (different file)
• Usually I use RollingFileAppender which can split logs to multiple files on its size, date, etc.

All of the above does not require any code change. All I want to achieve with configuration.