OK, I’ve found how to deal with it. At least, it’s one of possible solutions: int nFiles = (int) SendNppMsg(NPPM_GETNBOPENFILES, 0, 0); if ( !SendNppMsg(NPPM_DOOPEN, (WPARAM) 0, (LPARAM) params.c_str()) ) { nCmdResult = CMDRESULT_FAILED; DWORD dwAttr = ::GetFileAttributes(params.c_str()); if ( (dwAttr != INVALID_FILE_ATTRIBUTES) && ((dwAttr & FILE_ATTRIBUTE_DIRECTORY) == FILE_ATTRIBUTE_DIRECTORY) ) { // NPPM_DOOPEN unexpectedly returns 0 when a folder is specified // as its argument, though in fact it does open all the files // from that folder. int nFilesNow = (int) SendNppMsg(NPPM_GETNBOPENFILES, 0, 0); if ( nFilesNow != nFiles ) { nCmdResult = CMDRESULT_SUCCEEDED; } } }

Thanks for the reply Problem Statement: In my project, I do shell scripting and use notepad++ to write the script. I need to follow some rules while writing the code. Thus, I want to develop a plugin (which works like a code reviewer) which when selected in notepad++, could automatically check the code(script) at the run time while I am writing the code(script) in notepad++ and display an error message if any rule is not followed. For e.g. SELECT word should always be in upper case. So whenever I write SELECT word in small case in notepad++ then an error message should popup. Can you please suggest how should I go for it using C# template for plugin development?

The x64 at github you could add as pull request. For the access to the server you need the help of @bruderstein, but his is currently seldom around. I could copy the data of a x64 PR and create a corresponding entry.

Now also processes ANSI encoded SQL with special chars Regards Guido

I’ve made a couple, it should be pretty simple (it’s just a powershell script) The case which complicates things for putting any extension on there (including the plugin manager, but that might have some advantages) is what if when updating, Notepad++ is already open? The files are locked and the update will fail. It needs a way to schedule the update.

Look fine. With the version available from versioninfo the additional data: <versions> <version number="1.11.34" md5="56a19878b902d25d0c1b12b33d3ba44a"/> <version number="1.11.37" md5="b8dfbf18248c53b9d7e368e013590b55"/> </versions> is not necessary any longer. I corrected the validation for the x86 version. The click on add hash for the dll was missing in the webinterface. Currently the validation for x64 also fails. I think that is just a sync issue and should be fine in one hour.