.Net 6 based plugin

[Carlos Henrique Guardão Gandarez]

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?

[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.