Community

    • Login
    • Search
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    best way to get debug output while developing plugins?

    Plugin Development
    global extended chars difference
    4
    5
    967
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Dimple sharma
      Dimple sharma last edited by dail

      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 Eko palypse 2 Replies Last reply Reply Quote 0
      • Alan Kilborn
        Alan Kilborn @Dimple sharma last edited by

        @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

        1 Reply Last reply Reply Quote 1
        • Eko palypse
          Eko palypse @Dimple sharma last edited by 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 1 Reply Last reply Reply Quote 3
          • dail
            dail @Eko palypse last edited by

            @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 1 Reply Last reply Reply Quote 4
            • Eko palypse
              Eko palypse @dail last edited by

              @dail

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

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright © 2014 NodeBB Forums | Contributors