In order to enable your client software to upgrade this method, you need to do Form, algorithm, business logic, etc. that may change in the DLL. In fact, I usually make all things other than the first form of the system, all of them, who knows what may change? And the first FORM of the system I usually do is particularly simple, usually just a welcome page, no need to change.
Let's probably say what you need to do with SmartAssembly. First you need a server, all clients can connect to this server. Then you need to run IIS on this server and create a virtual directory. Finally, when a DLL has a new version, you only need to copy it into the directory on this server. Because the user runs a client program, it automatically searches in the virtual directory on the server, discovers the new version of the DLL, will automatically download and replace the old version of the DLL.
The name of the server's IP and all DLLs are specified in the configuration file, which is very easy to understand. And the whole process, you only need to add an additional code.
One line of code that needs to be added is:
Add the following code before the Application.run statement in the main function:
CONFIGURATIONSETTING.GETCONFIGHTNING.SMARTASSEMBLYCONFIG.SECTIONNAME); Application.run ();
The configuration file is as follows:
