Application program version management method and device and electronic equipment

Abstract

The invention relates to an application program version management method and device and electronic equipment, and the method comprises the steps: responding to a starting command of an application program client, sending a request message to a remote server, and obtaining a target version number returned by the remote server; determining whether application program version updating is executed or not according to a comparison result of the target version number and the current running version number; the remote server globally installs application programs for all users, and each version of application program uses a unique appId when being packaged and published; when application program updating needs to be executed, whether a configuration file exists in a current user document directory or not is checked; if yes, according to whether the application installation directory of the target version number exists in the configuration file or not, the target version application program is selected to be started or a registry is searched for; and if not, executing the creation of the configuration file. The application programs are globally installed on the remote server for all users, and a foundation is laid for multiple users to run the application programs in parallel.

Description

Technical Field

[0001] The present invention relates to the field of application technology, and in particular to an application version management method, device and electronic device. Background Art

[0002] For scenarios where applications need to be installed on remote Windows servers, in order to fully utilize the server's hardware resources, the multi-user working mode that comes with the Windows operating system is usually used, that is, each user runs the application in parallel, and each Windows user installs the application separately on the same server. Relatively speaking, this mode is suitable for scenarios where there are fewer servers to be deployed and the number of users on each server is not large.

[0003] In the actual application process of some projects, each Windows server usually has 8 or more users, and some projects have dozens of servers. If each Windows user installs the application separately, it will take a lot of time. Correspondingly, if a certain version of the application has a problem, the manual return workload is also very large, and the labor cost is too high. In addition, since each user storage is independent of each other, it will take up a lot of storage space, but in fact many users use the same version of the application, resulting in a waste of space.

[0004] For the above problem, you can choose to install it only once for each server, that is, not install it one by one according to Windows users, but at the same time, a new problem will arise, that is, the upgrade or downgrade of one user will affect the use of other users. In addition, all users must keep the same version number.

[0005] Therefore, providing a method that can reduce manpower time consumption, reduce storage space usage, and flexibly isolate the application version used by each Windows user is an urgent problem to be solved. Summary of the invention

[0006] In view of this, embodiments of the present application provide an application version management method, device, and electronic device to solve the above problems.

[0007] In a first aspect, an embodiment of the present application provides an application version management method, comprising the following steps:

[0008] Respond to the startup command of the application client, and send a request message to the remote server when starting to obtain the target version number returned by the remote server;

[0009] Determining whether to execute the application version update step according to the comparison result between the target version number and the currently running version number; wherein the application is globally installed for all users on the remote server, and each version of the application uses a unique appId when it is packaged and released;

[0010] When the application update step needs to be executed, check whether there is a configuration file in the document directory of the current user;

[0011] If it exists, then, according to whether the application installation directory of the target version number exists in the configuration file, the step of starting the target version application or the step of searching the registry is selected to execute;

[0012] If it does not exist, execute the step of creating the configuration file.

[0013] In some embodiments, the configuration file includes the target version of the current user, and the client startup path and root directory corresponding to the target version.

[0014] In some of the embodiments, the configuration file also includes the historical usage versions of the current user and the corresponding client startup path.

[0015] In some embodiments, the step of starting the target version application includes:

[0016] When the application installation directory of the target version number exists in the configuration file, the current version number recorded in the configuration file is correspondingly modified to the target version number;

[0017] Close the current version of the application and start the target version of the application.

[0018] In some embodiments, after closing the current version application and starting the target version application, the process further includes:

[0019] If a version modification instruction is received, the process returns to the step of searching the configuration file for the application installation directory of the target version number.

[0020] In some embodiments, the step of searching the registry comprises:

[0021] Searching the registry for an application installation directory with the target version number;

[0022] If it exists, updating the mapping relationship between the target version number and the application installation directory of the target version number to the configuration file;

[0023] If it does not exist, the target version application client download step of the remote server is executed.

[0024] In some embodiments, the target version application client downloading step of the remote server includes:

[0025] Requesting the remote server to download the target version application client according to the target version number, and downloading the corresponding application;

[0026] Create a directory with the target version number as the directory name under the root directory, and install the downloaded application into the directory;

[0027] After the installation is completed, the mapping relationship between the target version number and the corresponding application installation path is inserted into the configuration file, and the current version number in the configuration file is updated to the target version number.

[0028] In some embodiments, when executing the step of creating the configuration file, it includes:

[0029] A configuration file is created in the document directory of the current user; wherein the current version is the target version, the current client installation record is the root directory, and the installation directory mapping relationship corresponding to the current version is retained.

[0030] In a second aspect, an embodiment of the present application provides an application version management device, including:

[0031] The first unit is configured to respond to a startup command of the application client and send a request message to the remote server when starting to obtain a target version number returned by the remote server;

[0032] The second unit is configured to determine whether it is necessary to perform an application version update step according to a comparison result between the target version number and the currently running version number; wherein the application is globally installed for all users on the remote server, and each version of the application uses a unique appId when it is packaged and released;

[0033] The third unit is configured to check whether there is a configuration file in the document directory of the current user when the application update step needs to be performed;

[0034] The fourth unit is configured to select to execute the step of starting the target version application or the step of searching the registry according to whether the application installation directory of the target version number exists in the configuration file if it exists;

[0035] The fifth unit is configured to execute the step of creating the configuration file if the configuration file does not exist.

[0036] In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a storage medium, and a computer program, wherein the computer program is stored in the storage medium, and when the computer program is executed by the processor, it implements any of the above-mentioned application version management methods.

[0037] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements any of the above-mentioned application version management methods.

[0038] Technical effects of the present invention:

[0039] By installing applications globally for all users on the remote server, the foundation is laid for multiple users to run applications in parallel. Each server only needs to install one application, rather than installing it for each user separately, effectively reducing the labor cost and storage cost of installation, especially when there are multiple users on the server. In addition, by managing configuration files, version upgrades or downgrades for individual users can be achieved. That is, in a multi-user environment, each user's configuration file can record its specific application version information, providing a basis for subsequent version control.

[0040] Further features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments, features, and aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.

[0042] Figure 1 A flowchart of an application version management method according to an embodiment of the present application is shown;

[0043] Figure 2 A schematic diagram of a version update implementation process of an application version management method according to an embodiment of the present application is shown;

[0044] Figure 3 Shown is a structural block diagram of an application version management device according to an embodiment of the present application;

[0045] Figure 4 Shown is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0046] Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. The same reference numerals in the accompanying drawings represent elements with the same or similar functions. Although various aspects of the embodiments are shown in the accompanying drawings, the drawings are not necessarily drawn to scale unless otherwise specified.

[0047] The word “exemplary” is used exclusively herein to mean “serving as an example, example, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0048] In addition, in order to better illustrate the present disclosure, numerous specific details are given in the following specific embodiments. It should be understood by those skilled in the art that the present disclosure can also be implemented without certain specific details. In some examples, methods, means, components and circuits well known to those skilled in the art are not described in detail in order to highlight the subject matter of the present disclosure.

[0049] In the prior art, although manually installing applications under each Windows user can achieve the goal of each user not affecting each other, and the subsequent application upgrade or downgrade of each user can be realized by receiving requests, it is aimed at when there are relatively few servers to be deployed and the number of users per server is small. In the actual application process, some projects will have a scenario where the number of required servers and the number of Window users corresponding to each server are large. Based on this, installing applications one by one will cause a lot of time and energy to appear, and each user storage is independent of each other, occupying a large storage space. At the same time, since most users use the same version of the application, it is very easy to cause a waste of storage space. Therefore, the present application provides an application version management method, which realizes the version upgrade or downgrade of a single user through the management of configuration files. Each server only needs to install one application, and there is no need to repeat the installation for each user.

[0050] Embodiment 1

[0051] The present application embodiment provides an application version management method, Figure 1 is a flowchart of the steps of the application version management method according to an embodiment of the present application, such as Figure 1 As shown, the method comprises the following steps:

[0052] S100, responding to the startup command of the application client, and sending a request message to the remote server when starting, to obtain the target version number returned by the remote server;

[0053] In this step, when the local client starts according to the startup command, it will initiate a request to the server, in which the request message header contains the current user name. The server queries the target version client that the current client should run based on the user name in the message header, and returns it to the local client. That is, the server returns the target version number that the current client should run, so that the current client can determine whether to update the version.

[0054] S200, determining whether it is necessary to perform an application version update step according to a comparison result between the target version number and the currently running version number; wherein the application is globally installed for all users on the remote server, and each version of the application uses a unique appId when it is packaged and released;

[0055] In this step, the local client determines whether to update the application version according to the target version number returned by the remote server. Specifically, the local client compares the received target version number with the currently running version number. If they are the same, no processing is performed and the startup is continued; if they are different, the local configuration file needs to be matched according to the target version number, and the corresponding startup path is searched to update the client.

[0056] It should be noted that by installing applications globally for all users on the remote server, that is, storing all application versions on the remote server and supporting the download and installation of these versions, users can interact with the remote server through the application client to obtain the required application version, which lays the foundation for multiple users to run applications in parallel. Each server only needs to install one application, rather than installing it for each user separately, effectively reducing the installation labor cost and storage cost, especially when there are multiple users on the server.

[0057] In addition, it is important to emphasize that during the application packaging phase, each version of the package uses a unique appId, which is a unique identifier for the specified application. In other words, when multiple versions of an application are stored on the server, appId can help accurately identify each application and avoid confusion between different applications. When multiple applications are undergoing version management and update operations, appId can clearly tell which application is being operated, ensuring that version upgrades, downgrades, or other management operations are performed on the correct application.

[0058] S300, when it is necessary to execute the application version update step, check whether there is a configuration file in the document directory of the current user;

[0059] In this step, after starting the application, there is a preprocessing stage before the application works, that is, if the target version number returned by the server is different from the currently running version number, then the application client will read the current user, that is, a configuration file under the document directory of the current Windows user, and match it according to the version number. Here, it should be noted that before this, it is necessary to determine whether there is a configuration file under the user document. Specifically, each user's configuration file records the information related to the application version of the current Windows user, providing a basis for the control of subsequent versions. When upgrading or downgrading the version for individual users, it can be achieved by modifying the configuration file of the Windows user.

[0060] In some of the embodiments, the configuration file includes the target version of the current user, the client startup path and the root directory corresponding to the target version.

[0061] In this embodiment, the configuration file records the version that the current Windows user should use, that is, the target version, the client startup path corresponding to the target version, and the root directory where all versions of the client are installed. Here, it should be noted that the root directory is the directory where the client is first installed, and the installation directories of different versions of the client installed on the current host thereafter are subdirectories established under the root directory with the version number as the name. The above directory structure facilitates users and administrators to manage and maintain different versions of the client. When a specific version of the client needs to be found, the corresponding subdirectory can be quickly located through the root directory and the version number to improve the search efficiency.

[0062] In some of these embodiments, the configuration file also includes the historical usage versions of the current user and the corresponding client startup path.

[0063] In this embodiment, the configuration file records the version numbers and corresponding installation directories of all clients installed on the current Windows host, providing an important reference for client version management and facilitating users to switch between different versions. It will be automatically generated after the client is installed, recording the client version and installation path installed on the current computer. Specifically, in addition to the current user's target version and the corresponding client startup path, it also records the current user's historically used versions and the corresponding client startup path, providing convenience for version rollback of the application. For example, when a user upgrades to a new version and finds problems, such as software function anomalies, compatibility issues, etc., the historical version information in the configuration file can be used to roll back to the previous stable version to ensure normal use.

[0064] S410, if it exists, then according to whether there is an application installation directory with the target version number in the configuration file, select to execute the step of starting the target version application or the step of searching the registry;

[0065] In this step, if there is a configuration file in the document directory of the current user, the version number will be matched in the configuration file. If a match is found, it means that this version of the client has been installed on this computer and there is no need to download it separately. Just find the client according to the path and start it. If no match is found, it means that this version of the client has not been installed on the computer and a request will be made to the server to download the client with that version number to complete the update operation.

[0066] Specifically, the configuration file is searched to see whether there is an application installation directory with the target version number, and the step of starting the target version application or the step of searching the registry is selected according to the corresponding search results. Among them, if the application installation directory with the target version number can be found in the configuration file, that is, the target client information exists, then the step of starting the target version application is executed to ensure that the application can correctly start the target version; it should be noted that if it cannot be found in the configuration file, the registry is further searched. The registry here is the Windows registry, which is an important hierarchical database of the Windows operating system and its applications, used to store system and application settings information.

[0067] S420: If the configuration file does not exist, execute the step of creating a configuration file.

[0068] In this step, if there is no configuration file in the document directory of the current user, you need to create a configuration file to establish the version management basis for the user. For example, when using the application for the first time or the configuration file is lost, the configuration file cannot be found in the document directory of the current Windows user. At this time, creating a configuration file ensures that each user has his own version management record, so that users who use the application can smoothly perform version management and switching.

[0069] In some embodiments, the step of launching the target version application includes:

[0070] When the application installation directory with the target version number exists in the configuration file, the current version number recorded in the configuration file is modified to the target version number;

[0071] Close the current version of the application and start the target version of the application.

[0072] In this embodiment, after accessing the remote server to obtain the application version number that the current user should configure, that is, the target version number, if the version number currently running on the client is different from the target version number, it is necessary to determine in the configuration file whether the application installation directory of the target version number can be found. If it can, the client can be found according to the path and started. In addition, it is necessary to further modify the version number in the configuration file to the target version number. After updating to the target version number, the application will directly start the corresponding version according to the new version number information when it is started next time, that is, the above process will not be repeated.

[0073] It should be noted that the client sets up a polling sub-thread to continuously read the target version of the current user maintained on the back-end server. If it is detected that the target version has changed, it will first find the target version locally. If it cannot be found, the server download step will be executed. In this way, each Windows user can share the same version of the client without downloading it again.

[0074] In some embodiments, after closing the current version application and starting the target version application, the method further includes:

[0075] If a version modification instruction is received, the process returns to the step of searching the configuration file for the application installation directory of the target version number.

[0076] It should be noted that if the present embodiment receives a version modification instruction, it returns to the step of searching for the installation directory of the target version client in the configuration file, and determines whether the target client information exists in the configuration file, thereby determining whether to directly close the current client or to execute the step of searching the registry for client information. This forms a closed loop for the entire application version control process, and the application version of a single user can be adjusted at any time according to actual needs. Whether it is an upgrade or a downgrade, it can respond quickly without affecting the normal operation of other Windows accounts.

[0077] In some embodiments, the step of searching the registry includes:

[0078] Check the registry to see if there is an application installation directory with the target version number;

[0079] If it exists, the mapping relationship between the target version number and the application installation directory of the target version number is updated to the configuration file;

[0080] If it does not exist, execute the target version application client download step of the remote server.

[0081] In this embodiment, when the application installation directory cannot be found in the configuration file, the application installation directory of the target version number can be obtained by searching the registry. During the installation process, some applications will record their installation information in the registry, including the installation directory, etc. When the target version installation directory cannot be found in the configuration file, querying the registry provides another way to obtain the installation directory.

[0082] Specifically, if the target version's installation directory can be found in the registry, the mapping relationship between the target version number and the installation directory in the registry is updated to the current user profile, so that the profile can be kept updated, so that the next time the application is started, the correct installation directory can be directly obtained from the profile without having to search the registry again. If the target version's installation directory cannot be found in the Windows registry either, it is necessary to request the application to be downloaded from the server to ensure that the user can obtain the target version application that they ultimately need.

[0083] It should be noted that in actual application, the version number of each user is managed through the configuration file under each Windows user, and other versions of the client available on the current host can be shared between users through the Windows registry, without the need to re-download, saving time for switching versions. In addition, based on the multi-user mechanism of Windows, the operating system has already done a good job of isolating each user, and there is no need to spend extra time on isolation. At the same time, writing to the registry is also a mechanism of Windows itself, which can be completed by making reasonable use of the mechanism of the Windows operating system.

[0084] In some embodiments, the step of downloading the target version application program client of the remote server includes:

[0085] Request the target version application client from the remote server according to the target version number and download the corresponding application;

[0086] Create a directory with the target version number as the directory name in the root directory and install the downloaded application into the directory;

[0087] After the installation is complete, the mapping relationship between the target version number and the corresponding application installation path is inserted into the configuration file, and the target version number in the configuration file is updated.

[0088] In this embodiment, when the target version application installation directory cannot be found in the configuration file and the registry, it is necessary to request the target version application client from the remote server according to the target version number to meet the user's needs. Specifically, it is necessary to create a directory with the target version number as the name under the root directory, and install the downloaded application to this directory. It ensures that different versions of applications can be stored independently to avoid conflicts between versions.

[0089] Furthermore, after the installation is complete, a mapping relationship between the version number and the application installation path information is inserted into the configuration file, and the target version number of the configuration file is changed. That is, by updating the configuration file, the application can correctly find the newly installed version, ensuring that the new installed version can be used directly when it is started next time.

[0090] In some of the embodiments, when executing the step of creating a configuration file, it includes: creating a configuration file in the document directory of the current user; wherein the current version is the target version, the current client installation record is the root directory, and the installation directory mapping relationship corresponding to the current version is retained.

[0091] It should be noted that the configuration file plays a key role in the application version management process. The update of the configuration file mainly updates the client version of the current user, as well as the newly used client version and the corresponding application startup path. Therefore, if there is no configuration file, the system will not be able to accurately perform version upgrades, downgrades, and find the correct application startup path. When there is no configuration file, it is necessary to create it in the document directory of the current Windows user, where the current version is recorded as the target version, the current client installation record is recorded as the root directory, and the installation directory mapping relationship corresponding to the current version is retained. In this way, an initial version management system is created so that subsequent operations can be performed based on this version. Among them, recording the root directory can help the system quickly find the installation location of the application, and the installation directory mapping relationship provides an important reference for version upgrades and downgrades.

[0092] like Figure 2 As shown, a complete implementation example requiring version update will be provided below for detailed description.

[0093] Specifically, when the target version number is inconsistent with the current running version number, it is necessary to first check whether there is a configuration file in the current Windows user document directory;

[0094] If a configuration file exists, determine whether the client of this version has been installed based on the matching result of the target version number. If so, directly find the client and start it based on the application installation directory of the target version. After starting the target client, if a client version change is detected, return to the step of finding the installation directory of the target version client in the configuration file.

[0095] Among them, if the application installation directory cannot be found in the configuration file, it is further determined whether there is client information in the registry; if so, the client is found and started according to the corresponding path, and the mapping relationship between the version number and the installation path is updated to the configuration file; if the client information does not exist in the registry, a directory with the target version number as the directory name is created under the root directory, and it is downloaded from the remote server to the client and installed in the directory, and then the configuration file update step is executed.

[0096] If the configuration file does not exist, create one, record the target version and root directory, and keep the installation directory mapping relationship corresponding to the current version.

[0097] It can be seen that by adopting the method of the present application, each Windows host only installs the application once, which saves the labor cost consumption in the case of multiple hosts and multiple Windows users, and does not need to repeatedly install the same version of the application, effectively saving storage space. The version number of each user is managed through the configuration file under each Windows user, and the available other versions of the client on the current host are shared between users through the Windows registry, without the need to re-download, saving the time of switching versions.

[0098] Embodiment 2

[0099] like Figure 3 As shown, the embodiment of the present application provides an application version management device, including:

[0100] The first unit is configured to respond to a startup command of the application client and send a request message to the remote server when starting to obtain a target version number returned by the remote server;

[0101] The second unit is configured to determine whether it is necessary to perform an application version update step according to a comparison result between the target version number and the currently running version number; wherein the application is globally installed for all users on the remote server, and each version of the application uses a unique appId when it is packaged and released;

[0102] The third unit is configured to check whether there is a configuration file in the document directory of the current user when the application update step needs to be performed;

[0103] The third unit is configured to select to execute the step of starting the target version application or the step of searching the registry according to whether the target version number application installation directory exists in the configuration file if it exists;

[0104] The fourth unit is configured to execute the step of creating a configuration file if the configuration file does not exist.

[0105] Embodiment 3

[0106] like Figure 4 As shown, an embodiment of the present application provides an electronic device, which includes a processor, a storage medium and a computer program. The computer program is stored in the storage medium. When the computer program is executed by the processor, any of the above-mentioned application version management methods is implemented. Specific examples can refer to the examples described in the above-mentioned embodiments and optional implementation methods, and this embodiment will not be repeated here.

[0107] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0108] In addition, in combination with the application version management method in the above embodiment, the third embodiment of the present application can provide a storage medium for implementation. The storage medium stores a computer program; when the computer program is executed by the processor, any one of the application version management methods in the above embodiment is implemented, and the method includes:

[0109] Respond to the startup command of the application client, and send a request message to the remote server when starting to obtain the target version number returned by the remote server;

[0110] Determining whether to execute an application version update step according to a comparison result between the target version number and the currently running version number; wherein the application is globally installed for all users on the remote server, and each version of the application uses a unique appId when it is packaged and released;

[0111] When the application update step needs to be executed, check whether there is a configuration file in the document directory of the current user;

[0112] If it exists, the step of starting the target version application or searching the registry is selected according to whether the application installation directory of the target version number exists in the configuration file;

[0113] If it does not exist, proceed to create the configuration file.

[0114] Taking a processor as an example, the processor, memory, input device and output device in the electronic device can be connected via a bus or other methods, taking connection via a bus as an example.

[0115] As a computer-readable storage medium, the memory may include a high-speed random access memory, a non-volatile memory, etc., and may be used to store operating systems, software programs, computer executable programs, and databases, such as the program instructions / modules corresponding to the application version management method of Example 1 of the present invention, and may also include a memory, which may be used to provide an operating environment for operating systems and computer programs. In some instances, the memory may further include a memory remotely located relative to the processor, and these remote memories may be connected to the electronic device via a network.

[0116] The processor is used to provide computing and control capabilities, and may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application. The processor executes various functional applications and data processing of the electronic device by running computer executable programs, software programs, instructions, and modules stored in the memory, that is, implementing the application version management method of embodiment 1.

[0117] The output device of the electronic device can be a liquid crystal display or an electronic ink display, and the input device of the electronic device can be a touch layer covering the display, or a case, trackball or touchpad provided on the housing of a computer device, or an external keyboard, touchpad or mouse.

[0118] The electronic device may also include a network interface / communication interface, and the network interface of the electronic device is used for external terminals to communicate via a network connection. Examples of the above network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0119] Those skilled in the art will understand that Figure 4 The structure shown in the figure is only a partial structural block diagram related to the scheme of the present application, and does not constitute a limitation on the electronic device to which the scheme of the present application is applied. The specific electronic device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0120] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing related hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DD RSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink), DR AM (SDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0121] It is worth noting that in the embodiment of the application version management method, the various units and modules included are divided only according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.

[0122] Unless otherwise defined, the technical terms or scientific terms involved in this application should be understood by people with ordinary skills in the technical field to which this application belongs. The words "one", "one", "the" and the like involved in this application do not indicate a quantitative limitation and may represent the singular or plural. The terms "include", "comprise", "have" and any of their variations involved in this application are intended to cover non-exclusive inclusions. The words "connect", "connected", "coupled" and the like involved in this application are not limited to physical or mechanical connections, but include electrical connections, whether direct or indirect. The "multiple" involved in this application refers to two or more, and "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. The terms "first", "second", "third" and the like involved in this application are merely to distinguish similar objects and do not represent a specific ordering of objects.

[0123] The above embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but the limitation of the scope of the invention patent cannot be understood as a result. It should be pointed out that, for a person of ordinary skill in the art, several modifications or improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A method for managing application versions, characterized in that: The steps include: Respond to the startup command of the application client, and send a request message to the remote server when starting to obtain the target version number returned by the remote server; Determining whether to execute the application version update step according to the comparison result between the target version number and the currently running version number; wherein the application is globally installed for all users on the remote server, and each version of the application uses a unique appId when it is packaged and released; When the application update step needs to be executed, check whether there is a configuration file in the document directory of the current user; If it exists, then, according to whether the application installation directory of the target version number exists in the configuration file, the step of starting the target version application or the step of searching the registry is selected to execute; If it does not exist, execute the step of creating the configuration file.

2. The application version management method according to claim 1, characterized in that: The configuration file includes the target version of the current user, and the client startup path and root directory corresponding to the target version.

3. The application version management method according to claim 2, characterized in that: The configuration file also includes the historical usage version of the current user and the corresponding client startup path.

4. The application version management method according to claim 1, characterized in that: The step of starting the target version application program includes: When the application installation directory of the target version number exists in the configuration file, the current version number recorded in the configuration file is correspondingly modified to the target version number; Close the current version of the application and start the target version of the application.

5. The application version management method according to claim 4, characterized in that: After closing the current version application and starting the target version application, the method further includes: If a version modification instruction is received, the process returns to the step of searching the configuration file for the application installation directory of the target version number.

6. The application version management method according to claim 1, characterized in that: The step of searching the registry comprises: Searching the registry for an application installation directory with the target version number; If it exists, updating the mapping relationship between the target version number and the application installation directory of the target version number to the configuration file; If it does not exist, the target version application client download step of the remote server is executed.

7. The application version management method according to claim 6, characterized in that: The target version application client downloading step of the remote server includes: Requesting the remote server to download the target version application client according to the target version number, and downloading the corresponding application; Create a directory with the target version number as the directory name under the root directory, and install the downloaded application into the directory; After the installation is completed, the mapping relationship between the target version number and the corresponding application installation path is inserted into the configuration file, and the current version number in the configuration file is updated to the target version number.

8. The application version management method according to any one of claims 1 to 7, characterized in that: When executing the step of creating the configuration file, it includes: A configuration file is created in the document directory of the current user; wherein the current version is the target version, the current client installation record is the root directory, and the installation directory mapping relationship corresponding to the current version is retained.

9. An application version management device, characterized in that: include: The first unit is configured to respond to a startup command of the application client and send a request message to the remote server when starting to obtain a target version number returned by the remote server; The second unit is configured to determine whether it is necessary to perform an application version update step according to a comparison result between the target version number and the currently running version number; wherein the application is globally installed for all users on the remote server, and each version of the application uses a unique appId when it is packaged and released; The third unit is configured to check whether there is a configuration file in the document directory of the current user when the application update step needs to be performed; The fourth unit is configured to select to execute the step of starting the target version application or the step of searching the registry according to whether the application installation directory of the target version number exists in the configuration file if it exists; The fifth unit is configured to execute the step of creating the configuration file if the configuration file does not exist.

10. An electronic device comprising a processor, a storage medium and a computer program, wherein the computer program is stored in the storage medium, wherein: When the computer program is executed by a processor, the application version management method according to any one of claims 1 to 8 is implemented.

Images