Community
    • Login

    .Net 6 based plugin

    Scheduled Pinned Locked Moved
    Notepad++ & Plugin Development
    2
    2
    464
    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.
    • Carlos Henrique Guardão GandarezC
      Carlos Henrique Guardão Gandarez
      last edited by

      Hi all!

      I started revamping a legacy plugin written in .Net full framework v4.8 to the new .Net 6. After implementing all interfaces isUnicode, setInfo, getFuncsArray, messageProc, getName and beNotified it still throws an unhandled and too generic error from npp Failed to load. I’m developing and testing in the same machine, so I assume .Net 6 runtime is installed and available. Is there any trick to support .Net “Core” or only the plugins developed under .Net full framework are supported?

      R 1 Reply Last reply Reply Quote 0
      • R
        rdipardo @Carlos Henrique Guardão Gandarez
        last edited by rdipardo

        @Carlos-Henrique-Guardão-Gandarez,

        or only the plugins developed under .Net full framework are supported?

        Afraid so.

        Every plugin is fundamentally limited to whatever APIs are used by Notepad++ itself. From the very beginning, those APIs have been the oldest, lowest-level ones available.

        Microsoft’s legacy .NET Framework is guaranteed to be installed on every Windows device from Vista onward, which is why the “official” .NET plugin template exclusively targets it.

        As the template’s maintainers recently admitted on GitHub, being stuck with such an old runtime is a technical debt that all .NET plugin developers just have to put up with.

        1 Reply Last reply Reply Quote 3
        • First post
          Last post
        The Community of users of the Notepad++ text editor.
        Powered by NodeBB | Contributors