C# SolidWorks secondary development API---package registration and distribution of plug-ins

After completing the development of the plug-in, we need to distribute the software to the user's machine.
There are generally two methods I use:

  1. Direct plug-in registration:
    This is also my most common method. Just use the installer to register the plug-in and reopen solidworks.
    There is a condition for using this, that is, your other dlls are directly callable by .net and do not need to be registered again. As far as the current understanding is concerned, this tool can be used directly in most cases.
    If you have other needs, you can also modify this tool to perform operations, such as creating paths and copying files during batch installation.

    Download path: https://gitee.com/painezeng/SolidWorksAddinInstaller Insert picture description here

  2. Making the installation package:
    This situation feels a bit more high-end, you can generate the installation package in the msi format, just like other software downloaded on the Internet, it needs to be installed, and the company's IT can push and install the plug-ins in batches.
    In this way, I often use Inno Setup 5 software to make installation packages. Its function is relatively powerful, everyone can learn by themselves.
    Its advantage is that when there are many files that need to be packed, the compression ratio is still good.
    It can generate shortcuts, plug-in registration, file release, program menu generation, automatic generation of deleted program information, which can be displayed in the windows program list.
    You can set up multiple language files, and display various license information during installation.

Guess you like

Origin blog.csdn.net/zengqh0314/article/details/105925462