Installing a plugin is a process like this:
1. A plugin is understood as a file package, which can be placed anywhere, such as C:\1.dll
2. After the SW installation is complete, Windows needs to be notified, informing it that SW is now present in the system. The notification relies on the registry, which records the locations of some SW files.
3. Installing the plugin involves notifying SW that C:\1.dll belongs to you, and you need to keep me in mind. Therefore, add another record in the SW registry of Windows. When SW starts up, because of this record, 1.dll will be installed along with the plugin.
That’s all there is to it. If 1.dll and sw determine that this thing is illegal and unusable for our household, we won’t bring 1.dll along, and the plugin won’t load. That’s it.
The one you had before cannot be upgraded. It indicates that there is a C:\1.dll in the software, which is an old version. For some reasons, 1.dll should be updated to version 17, but in fact, it is still old.
Delete this 1.dll and replace it with a new one, and that’s it
In this process, the registry serves solely as a guiding function, and it does not distinguish whether a 1.dll file is new or old.
In the past, there were some functions that worked fine for others but not for you. For example, the quick rename function worked fine for others but not for you, because the sw API had bugs in different versions and under different sp patches.
In SW, there are often multiple ways to achieve a task. For example, I can use a notification menu, such as the word “complete”. I can accomplish this using SW’s API, or I can use .NET’s MessageBox.
I found a problem with the API, and I will implement the same thing in a different way.
The plugin requires API support. This API is not a file from our software, but a SW file from your computer. The plugin merely notifies SW that you want to use your file A for that purpose. If there’s a problem with your file, I can’t help you.
Here’s a premise: I have to know that there’s indeed a problem with the API before I proactively replace the method. The meaning of replacing the method is that I tell SW to use file B to do that task, bypassing A
Methods are not limitless; they are related to our level of expertise. If I don’t know where the problem lies, I can’t prescribe the right remedy.
You need an administrator because not everything is a program that Windows trusts. You have to tell Windows to trust everything it does. It can do whatever it wants, and it’s only allowed to replace 1.dll,
The “delete” I wrote above doesn’t mean you have to delete or uninstall. There is a logic to uninstalling, and I am just simplifying the process