[update] Pluginpack updated to v0.92.76
Kasper Graversen last edited by
Get your copy today: https://github.com/kbilsted/NotepadPlusPlusPluginPack.Net/releases
there a few minor breaking changes. but mostly A LOT of new definitions for accessing new areas of notepad++ functionality.
AdrianHHH last edited by
Thank you for creating the new plugin pack. Unfortunately I am having some challenges in using it and I would welcome your comments on what I am doing wrong.
First a minor observation on the installation notes. In the “README.md” file at section “Getting started” 2: When we copy the NppPlugin[version].zip file should we keep the version number in the file name or should we rename it to NppPlugin.zip? I just copied the file and kept the version number, that seemed to work.
I created a new project using the template. It defaults to .NET 3.5.2 which is not on my computer, so I changed the project to target 4.6.1.
Tried to build the project without making any changes and without adding any of the code of my plugin. Get two errors:
1>[[...]]\Main.cs(19,31,19,41): error CS0103: The name 'Properties' does not exist in the current context 1>[[...]]\Main.cs(20,37,20,47): error CS0103: The name 'Properties' does not exist in the current context
against these two lines:
static Bitmap tbBmp = Properties.Resources.star; static Bitmap tbBmp_tbTab = Properties.Resources.star_bmp;
File “Main.cs” has the line “namespace Kbg.NppPluginNET” (for class Main). Comparing to the Demo project, file “Demo.cs” has the line “namespace Kbg.Demo.Namespace” and in the demo project file “Resources.Designer.cs” has the line “namespace Kbg.Demo.Namespace.Properties”.
In my project I changed the namespace names in files “UnmanagedExports.cs” and “Resources.Designer.cs” to match my project. Also I added a “using Kbg.NppPluginNET;” to file “Main.cs” so that “frmMyDlg” in the line “static frmMyDlg frmMyDlg = null;” is available.
It would be useful if the installation notes could give some guidance on which files and classes should use which namespaces.
Building the solution gives the error:
1>[[...]]\PluginInfrastructure\DllExport\NppPlugin.DllExport.targets(8,5): error MSB4062: The "NppPlugin.DllExport.MSBuild.DllExportTask" task could not be loaded from the assembly [[...]]\PluginInfrastructure\DllExport\NppPlugin.DllExport.MSBuild.dll. Could not load file or assembly 'Microsoft.Build.Utilities, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
I find this message from Visual Studio very confusing. The text “UsingTask” does not seem to be in any of the files in the solution, nor can I find “Microsoft.Build.Utilities” or “ITask”.
Next I installed .NET 3.5.2 and then the build does not report the above error. Now the build fail with the message:
1>AfterBuild: 1> Cannot find lib.exe in 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\\..\..\VC\bin'.
There is no “lib.exe” in any of the sub-directories of “Microsoft Visual Studio 14.0” on my computer, but there are versions in the correct sub-directories of both “Microsoft Visual Studio 11.0” and “Microsoft Visual Studio 12.0”.
I also tried building the demo project and it also fails to find “lib.exe”.
Environment is Windows 10 with Microsoft Visual Studio Enterprise 2015 Version 14.0.25123.00 Update 2.
Kasper Graversen last edited by
Hi just got home from vacation. Any luck in my absence?
Please feel frwe to add more notes to the readme. Just edit it. I have only tested the plugin pack on my own computer… but it looks like paths should ve adjusted after installation… or multiple versions should be made. If that we need to automate this with a script. If you have not lost hope of writing plugins do write again and we can dig into your issues you are facing. Just crospost your mail here as an issue on github so i know you are still around