I learned the design and implementation of the <plug-in GIS application development framework> and compiled some plug-ins into DLL files.CodeA lot of details are easy to make mistakes,
For example, when the file name of the tool icon is generated, an exception occurs. However, the exception information can only be provided to find out which plug-in has encountered an exception and which line of code cannot be obtained,
Very depressed. At the beginning, I started to guess and guess the effect on my mood.
Then a simulation interface is created to directly call the relevant classes in the plug-in project and add them. After the simulation framework is set up, you can access the DLL debugging.
Method:
Right-click the DLL project and choose nbgis. maintools> Properties> Generate> output: Output path. The path is set to the location where the DLL is referenced, that is, \ nbgis. in the maingis \ bin \ debug \ plugin folder
Go to DLL debugging.
In this way, after each modification is made in the maintools folder, the related dll can be placed in the plugin folder after generation, without the need to copy and paste it each time.