best way to get debug output while developing plugins?

[Dimple sharma]

What is the best way to get debug output while developing plugins?

I am new to Notepad++ plugin development, and can’t seem to find any good way to debug my plugin.

[Alan Kilborn]

@Dimple-sharma

Well, running under a IDE capable of single-step debugging would be best. Depending upon what exactly your need is, perhaps OutputDebugString would work? https://msdn.microsoft.com/en-us/library/windows/desktop/aa363362(v=vs.85).aspx

[Eko palypse]

@Dimple-sharma

The most comfortable way would be to build a project with npp, scilexer and your plugin in VS2017.
Configure your output paths accordingly - done.
Note, only debug builds allow to use unsigned SciLexer dll.
If you want to test a release build you need to copy over an official SciLexer dll or modify
the necessary code in npp.

[dail]

@Eko-palypse

I always debug mine by setting VS to copy the built DLL file to Notepad++'s plugin directory, then set the notepad++.exe as the application to start debugging (no need to build N++ or SciLexer). You cant step through Notepad++ but you can step through the plugin code (which has always been sufficient for what I need).

[Eko palypse]

@dail

Thank you, very much appreciated - yes, that might be the easiest way to debug plugins.