You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 13, 2024. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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
andbeNotified
it still throws an unhandled and too generic error from nppFailed 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?The text was updated successfully, but these errors were encountered: