TWI416410B - System and method for updating version of the executable file - Google Patents

Abstract

The present invention provides a method for updating version of the executable file. The method includes: setting a time of source code to be compiled; reading attribute of the source code and the executable file; compiling the source code thereby generating a executable file in set time, if the attribute of the source code is not similar with the attribute of the executable file; updating the executable file in server if compiling is successful; amending the version of generated executable file; reading the version of the executable file in server when starting up the executable file in client computer; updating the executable file into the client computer if the version of the executable file in client computer is not the same with the version of the executable file in server. A system for updating version of the executable file is also provided.

Description

Executable version update system and method

The present invention relates to an executable file version update system and method.

In C/S (client/server) mode, the structural hierarchy of the application system is embodied in two layers, that is, the first layer is the executable file installed on the client side, and the second layer is the server combined through the network. It is characterized by strong data interaction and provides a more secure access mode.

However, since the C/S mode is an application running on multiple clients, when the system needs function expansion, modification, etc., the code of the application system needs to be recompiled, and the compiled executable files are copied to the user one by one. Reinstalling the end, so waste of manpower, can not guarantee the synchronization of system functions, and if the user copies at the same time, it will cause the server to be crowded and even cause the server to crash.

In view of the above, it is necessary to provide an executable file version update system, which can automatically update the latest version of the executable file on the server to the client after the client launches the corresponding executable file.

In addition, it is necessary to provide an executable file version update method that can be used After the client starts the corresponding executable file, it automatically updates the latest version of the executable file on the server to the client.

An executable file version updating system includes a server and a client computer, and the server includes: a setting module, configured to set the source code when the user stores the source code of the executable file on the server. a compiling time; the reading module is configured to read the attribute information in the source code and the attribute information of the executable file corresponding to the source code stored in the server; the determining module is configured to determine the read source code The attribute information is consistent with the attribute information of the executable file corresponding to the source code stored in the server; the compiling module is used to compile the settings when the attribute information in the source code and the attribute information in the executable file are inconsistent. Time to compile the source code to make it an executable file; update the module to update the executable file on the server to be consistent with the successfully compiled executable file when the source code is successfully compiled; a group, configured to modify a version number of the executable file generated after the successful compilation; the client computer includes: an acquisition module, configured to start the user terminal The executable file obtains the version number of the corresponding executable file in the server; the comparison module is configured to compare the version number of the executable file started on the client computer with the version number of the corresponding executable file on the server Is it consistent; the download module is used to download the executable file on the server to the client computer when the version number of the executable file started on the client computer is inconsistent with the version number of the corresponding executable file on the server. And install the executable.

An executable file version update method, the method comprising the following steps: when a user stores a source code that needs to generate an executable file on a server, setting a compile time of the source code; reading attribute information in the source code and Store the source generation in the server The attribute information of the executable file corresponding to the code; when the attribute information in the source code is inconsistent with the attribute information of the executable file corresponding to the source code stored in the server, the source code is compiled at the set time to make it Execute the file; when the source code is successfully compiled, update the executable file on the server to be consistent with the successfully compiled executable file; modify the version number of the executable file generated after successful compilation; when the user computer is started When the executable file is read, the version number of the corresponding executable file in the server is read; when the version number of the executable file started on the client computer does not match the version number of the corresponding executable file on the server, the server is The executable file is downloaded to the client computer and the executable file is installed.

Compared with the prior art, it can automatically update the latest version of the executable file on the server to the client after the user launches the corresponding executable file, thereby avoiding the artificial update of the executable file, improving efficiency and saving. Server resources.

1‧‧‧User computer

2‧‧‧Network

3‧‧‧Server

101‧‧‧Getting module

102‧‧‧Comparative Module

103‧‧‧Download module

301‧‧‧Setup module

302‧‧‧Reading module

303‧‧‧Judgement module

304‧‧‧Compile module

305‧‧‧Update Module

306‧‧‧Modified module

307‧‧‧Write module

S10‧‧‧ When the user stores the source code of the executable file on the server, set the compile time of the source code.

S11‧‧‧ reading the attribute information in the source code and the attribute information of the executable file corresponding to the source code stored in the server

S12‧‧‧Identifies whether the source code is consistent with the attribute information of the executable file

S13‧‧‧ Compile the source code at the set time to make it executable

S14‧‧‧Determine whether the compilation was successful

S15‧‧‧Update the executable file on the server to match the successfully compiled executable file

S16‧‧‧Modify the version number of the executable file generated after successful compilation

S17‧‧‧ The client computer obtains the version number of the corresponding executable file in the server

S18‧‧‧Comparison whether the version number of the client executable file is the same as the version number of the server executable file

S19‧‧‧Download the executable file on the server to the client computer and install the executable file

S20‧‧‧Write the exception report to the log file and notify the administrator

1 is a hardware framework diagram of a preferred embodiment of an executable file version update system of the present invention.

2 is a functional block diagram of a preferred embodiment of an executable file version update system of the present invention.

3 is a flow chart of a preferred embodiment of an executable file version updating method of the present invention.

FIG. 1 is a hardware architecture diagram of a preferred embodiment of an executable file version update system of the present invention. The system includes a client computer 10, a network 20, and a server 30. The server 30 can be a personal computer, a web server, or any other suitable computer.

In addition, the server 30 is connected to at least one client computer 10 through the network 20. The client computer 10 is used to provide an interactive interface to the user, which is convenient for the user to operate and the latest in the server 30 during operation. The executable file version is updated to the client computer 10. The network 20 can be an internet, a local area network, or a wireless communication network.

2 is a functional block diagram of a preferred embodiment of the executable file version update system of the present invention. The server 30 includes a setting module 301, a reading module 302, a determining module 303, a compiling module 304, an updating module 305, a modifying module 306, and a writing module 307. The client computer 10 includes a reading module 101, a comparison module 102, and a download module 103. The module referred to in the present invention is a computer program segment for performing a specific function, and is more suitable for describing the execution process of the software in the computer than the program. Therefore, the following description of the software is described in the module.

The setting module 301 is configured to set a compile time of the source code when the user stores the source code that needs to generate the executable file on the server. The user can set it at any time as needed, usually to reduce the load on the server 30, improve the processing efficiency of the server 30, and set the compile time when the server 30 has fewer data processing tasks.

The reading module 302 is configured to read the attribute information in the source code and the attribute information of the executable file corresponding to the source code stored in the server 30. The attribute information includes the date of writing, the date of modification, and the author. If the executable file corresponding to the source code stored in the server 30 does not exist, the attribute information of the executable file is empty.

The determining module 303 is configured to determine attribute information and a server in the read source code. In 30, the attribute information of the executable file corresponding to the source code is consistent.

The compiling module 304 is configured to compile the source code at a set compile time when the attribute information in the source code and the attribute information of the executable file corresponding to the source code stored in the server 30 are inconsistent. executable file. In the preferred embodiment, there are two ways to compile, one is incremental compilation, that is, only the source code written by the newly added function is compiled, and the other is fully compiled, that is, the source is written. The code is compiled all. Usually, the method of compiling is to find out whether there is a corresponding executable file in the directory where the executable file is stored. If there is a corresponding executable file, it is incrementally compiled. If the corresponding executable file does not exist, Compile completely.

The update module 305 is configured to update the executable file on the server to be consistent with the successfully compiled executable file when the source code is successfully compiled. According to the different way of compiling the source code, there are two ways to update. If the compilation method is incremental compilation, the executable file generated after successful compilation will overwrite the executable file corresponding to the source code. For complete compilation, the executable file generated after successful compilation is stored in the directory where the server 30 stores the executable file.

The modification module 306 is configured to modify the version number of the executable file generated after the compilation is successful. In the preferred embodiment, the modification manner is: if the compilation succeeds once, the version number is incremented by a number. Specifically, the version number of the original executable file is 1.1, and if the compilation is successful, a new one is generated. Executable file, the version number is changed to 1.2. However, depending on the situation, in other embodiments, the user may set other ways to modify the version number, for example, to modify the version number in a decreasing manner.

The write module 307 is configured to write an exception report to the log file when the source code fails to be compiled, and notify the administrator. In the preferred embodiment, the manner of notification is to notify the administrator in the form of a mail.

The obtaining module 101 is configured to obtain a version number of a corresponding executable file in the server 30 when the executable file of the client computer 10 is started. Usually, the executable file installed on the client computer has a corresponding icon. When the user clicks on the icon, the corresponding executable file is started, and then the obtaining module 101 automatically obtains the version of the executable file on the server 30. number. Specifically, it is assumed that the user needs to use a certain software (for example, a browser), click the browser icon, and start the executable file corresponding to the browser, and then the user computer 10 automatically obtains the corresponding browser on the server 30. The version number of the executable file.

The comparison module 102 is configured to compare whether the version number of the executable file started on the client computer 10 is consistent with the version number of the corresponding executable file on the server 30.

The download module 103 is configured to download the executable file on the server 30 to the user when the version number of the executable file started on the client computer 10 does not match the version number of the corresponding executable file on the server 30. End the computer 10 and install the executable.

3 is a flow chart of a preferred embodiment of an executable file version updating method of the present invention.

First, in step S10, when the user stores the source code that needs to generate the executable file on the server, the setting module 301 sets the compile time of the source code. The user can set it at any time as needed, usually to reduce the load on the server 30 and improve The processing efficiency of the server 30 sets the compile time when the server 30 has fewer data processing tasks.

In step S11, the reading module 302 reads the attribute information in the source code and the attribute information of the executable file corresponding to the source code stored in the server 30. The attribute information includes the date of writing, the date of modification, and the author. If the executable file corresponding to the source code stored in the server 30 does not exist, the attribute information of the executable file is empty.

In step S12, the determining module 303 determines whether the attribute information in the read source code is consistent with the attribute information of the executable file corresponding to the source code stored in the server 30.

In step S13, when the attribute information in the source code and the attribute information in the executable file are inconsistent, the compiling module 304 compiles the source code at the set time to make it an executable file. In the preferred embodiment, there are two ways to compile, one is incremental compilation, that is, only the source code written by the newly added function is compiled, and the other is fully compiled, that is, the source is written. The code is compiled all. Usually, the method of compiling is to find out whether there is a corresponding executable file in the directory where the executable file is stored. If there is a corresponding executable file, it is incrementally compiled. If the corresponding executable file does not exist, Compile completely.

In step S14, it is judged whether the compilation is successful. If the compilation is successful, an executable file is generated. If the compilation is unsuccessful, the process proceeds to step S20, an exception is indicated, the exception report is written to the log file, and the administrator is notified in time. In the preferred embodiment, the manner of notification is to notify the administrator in the form of a mail.

In step S15, when the source code is successfully compiled, the update module 305 updates the executable file on the server to be consistent with the successfully compiled executable file. According to the source code There are two ways to update the compiler. If the compilation method is incremental compilation, the executable file generated after successful compilation will overwrite the executable file corresponding to the source code. If the compilation method is fully compiled, The executable file generated after the successful compilation is stored in the directory where the server 30 stores the executable file.

In step S16, the modification module 306 modifies the version number of the executable file generated after the compilation is successful. In the preferred embodiment, the modification manner is: if the compilation succeeds once, the version number is incremented by a number. Specifically, the version number of the original executable file is 1.1, and if the compilation is successful, a new one is generated. Executable file, the version number is changed to 1.2. However, depending on the situation, in other embodiments, the user may set other ways to modify the version number, for example, to modify the version number in a decreasing manner.

In step S17, when the executable file of the client computer 10 is started, the obtaining module 101 acquires the version number of the corresponding executable file in the server 30. Usually, the executable file installed on the client computer has a corresponding icon. When the user clicks on the icon, the corresponding executable file is started, and then the acquisition module 101 automatically obtains the executable file on the server 30. version number. Specifically, it is assumed that the user needs to use a browser, click the icon corresponding to the browser, and start the executable file corresponding to the browser, and then the client computer 10 automatically reads the version number of the executable file corresponding to the browser on the server 30. .

In step S18, the comparison module 102 determines whether the version number of the executable file started on the client computer 10 is consistent with the version number of the corresponding executable file on the server 30.

In step S19, when the version number of the executable file started on the client computer 10 does not match the version number of the corresponding executable file on the server 30, the download module 103 will serve The executable file on the server 30 is downloaded to the client computer 10 and the executable file is installed.

In step S12, when the attribute information in the source code and the attribute information in the executable file match, the flow is directly ended.

In step S18, when the version number of the executable file started on the client computer 10 coincides with the version number of the corresponding executable file on the server 30, the flow is directly ended.

It should be noted that the above embodiments are only intended to illustrate the technical solutions of the present invention and are not intended to be limiting, and the present invention will be described in detail with reference to the preferred embodiments thereof The technical solutions are modified or equivalently substituted without departing from the spirit and scope of the technical solutions of the present invention.

S10‧‧‧ When the user stores the source code of the executable file on the server, set the compile time of the source code.

S11‧‧‧ reading the attribute information in the source code and the attribute information of the executable file corresponding to the source code stored in the server

S12‧‧‧Identifies whether the source code is consistent with the attribute information of the executable file

S13‧‧‧ Compile the source code at the set time to make it executable

S14‧‧‧Determine whether the compilation was successful

S15‧‧‧Update the executable file on the server to match the successfully compiled executable file

S17‧‧‧Modify the version number of the executable file generated after successful compilation. ‧‧S16 client computer obtains the version number of the corresponding executable file in the server

S18‧‧‧Comparison whether the version number of the client executable file is the same as the version number of the server executable file

S19‧‧‧Download the executable file on the server to the client computer and install the executable file

S20‧‧‧Write the exception report to the log file and notify the administrator

Claims (6)

An executable file version updating system includes a server and a client computer, and the server includes: a setting module, configured to set the source code when the user stores the source code of the executable file on the server. a compiling time; the reading module is configured to read the attribute information in the source code and the attribute information of the executable file corresponding to the source code stored in the server; the determining module is configured to determine the read source code The attribute information is consistent with the attribute information of the executable file corresponding to the source code stored in the server; the compiling module is used to compile the settings when the attribute information in the source code and the attribute information in the executable file are inconsistent. Time to compile the source code to make it an executable file. The compilation method includes incremental compilation of the source code written by the newly added function and full compilation of the compiled source code. The module is used to update the executable file on the server when the source code is successfully compiled. If the compilation mode is incremental compilation, it will be compiled into The generated executable file overwrites the executable file corresponding to the source code. If the compiled mode is fully compiled, the executable file generated after the successful compilation is stored in a directory used by the server for storing the executable file, so that Consistent with the compiled executable file; the modification module is configured to modify the version number of the executable file generated after the successful compilation; the client computer includes: an acquisition module, which is used to start the execution of the client computer Get the server when the file is The version number of the corresponding executable file; the comparison module is configured to compare whether the version number of the executable file started on the client computer is consistent with the version number of the corresponding executable file on the server; the download module is used to download When the version number of the executable file started on the client computer does not match the version number of the corresponding executable file on the server, the executable file on the server is downloaded to the client computer, and the executable file is installed. For example, in the executable file version update system described in claim 1, the attribute information includes an author, a date on which the source code is written, and a date of modification. The executable file version update system of claim 1, wherein the server further includes a write module, wherein the write module is configured to write an exception report to the log file when the source code fails to be compiled. And notify the administrator. An executable file version update method, the method comprising the following steps: when a user stores a source code that needs to generate an executable file on a server, setting a compile time of the source code; reading attribute information in the source code and The server stores the attribute information of the executable file corresponding to the source code; when the attribute information in the source code is inconsistent with the attribute information of the executable file corresponding to the source code stored in the server, the source code is performed at the set time. Compile and make it an executable file. The compilation method includes incremental compilation of the source code written by the newly added function and full compilation of the compiled source code. When the source code is compiled successfully, Update the executable file on the server. If the compilation method is incremental compilation, the executable file generated after successful compilation will overwrite the executable file corresponding to the source code. If the compilation mode is fully compiled, the compilation will be successful. Rear The generated executable file is stored in the directory where the server is used to store the executable file, so that it is consistent with the successfully compiled executable file; the version number of the executable file generated after the successful compilation is modified; when the user computer is started When the executable file is read, the version number of the corresponding executable file in the server is read; when the version number of the executable file started on the client computer does not match the version number of the corresponding executable file on the server, the server is The executable file is downloaded to the client computer and the executable file is installed. The method for updating an executable file version as described in claim 4, wherein the attribute information includes an author, a date on which the source code is written, and a date of modification. The method for updating an executable file version described in claim 4, the method further comprising the steps of: writing an exception report to a log file and notifying an administrator when the source code fails to compile.