Automated modification of pre-generated MSI packaged applications
First Claim
1. A method, comprising:
- preparing a deployment package for a unique instance via copying a first deployment package to a second deployment package automatically and changing an identifier or a parameter within the second deployment package automatically such that the second deployment package is unique from the first deployment package at least via a unique identifier;
creating an executable file for the unique instance, wherein creating the executable file comprises creating a dynamic link library (DLL);
generating a class file corresponding to the unique instance by a standalone application; and
compiling the class file with an external application to create the DLL;
updating a configuration file for the unique instance; and
packaging the executable file and the configuration file with the deployment package to create the unique instance of the deployment package for a unique copy of an existing application.
10 Assignments
0 Petitions
Accused Products
Abstract
Deployment packages for applications may be created automatically to deploy unique instances of an application for execution on a computer system. The deployment packages may be created by copying an original deployment package to a new deployment package and modifying properties, attributes, and/or values within the new deployment package. The modified parameters may include a globally-unique identifier (GUID). The modifications to the new deployment package may be performed automatically without access to source code for the application in the original deployment package. The new deployment package may be deployed on a computer system to install a unique instance of the application. Automatic creation of deployment packages may be useful for testing multiple copies of an application in parallel on a computer system.
56 Citations
14 Claims
-
1. A method, comprising:
-
preparing a deployment package for a unique instance via copying a first deployment package to a second deployment package automatically and changing an identifier or a parameter within the second deployment package automatically such that the second deployment package is unique from the first deployment package at least via a unique identifier; creating an executable file for the unique instance, wherein creating the executable file comprises creating a dynamic link library (DLL); generating a class file corresponding to the unique instance by a standalone application; and
compiling the class file with an external application to create the DLL;updating a configuration file for the unique instance; and packaging the executable file and the configuration file with the deployment package to create the unique instance of the deployment package for a unique copy of an existing application. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A computer program product, comprising:
a non-transitory computer readable medium comprising; code to prepare a deployment package for a unique instance via copying a first deployment package to a second deployment package automatically and changing an identifier or a parameter within the second deployment package automatically such that the second deployment package is unique from the first deployment package at least via a unique identifier; code to create an executable file for the unique instance, wherein the code to create the executable file for the unique instance comprises code to create a dynamic link library (DLL); code to generate a class file corresponding to the unique instance by a standalone application; and
code to compile the class file with an external application to create the DLL;code to update a configuration file for the unique instance; and code to package the executable file and the configuration file with the deployment package to create the unique instance of the deployment package for a unique copy of an existing application. - View Dependent Claims (8, 9, 10, 11)
-
12. An apparatus, comprising:
-
a memory; and a processor coupled to the memory, in which the processor is configured; to prepare a deployment package for a unique instance via copying a first deployment package to a second deployment package automatically and changing an identifier or a parameter within the second deployment package automatically such that the second deployment package is unique from the first deployment package at least via a unique identifier; to create an executable file for the unique instance;
to create dynamic link library (DLL);to generate a class file corresponding to the unique instance by a standalone application; and
to compile the class file with an external application to create the DLL;to update a configuration file for the unique instance; and to package the executable file and the configuration file with the deployment package to create the unique instance of the deployment package for a unique copy of an existing application. - View Dependent Claims (13, 14)
-
Specification