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.
2. The method of claim 1 , in which the step of packaging comprises creating a Microsoft installer package (MSI).
3. The method of claim 1 , in which the step of updating the configuration file comprises at least one of: updating the configuration file with a different system name; updating the configuration file with an alternate name; updating the configuration file with a different package name; updating the configuration file with a different program identification.
4. The method of claim 1 , in which the step of creating the DLL comprises: extracting an original DLL from the deployment package; and editing assembly code in the DLL to correspond to the unique instance.
5. The method of claim 1 , in which the step of creating the DLL comprises: generating source code corresponding to the unique instance for the DLL with a code generator; and compiling the source code into the DLL with the code generator.
6. The method of claim 1 , further comprising executing the deployment package on a hypervisor-based platform.
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.
8. The computer program product of claim 7 , in which the medium further comprises code to create a Microsoft installer package (MSI).
9. The computer program product of claim 7 , in which the medium further comprises at least one of: code to update the configuration file with a different system name; code to update the configuration file with an alternate name; code to update the configuration file with a different package name; code to update the configuration file with a different program identification.
10. The computer program product of claim 7 , in which the medium further comprises: code to extract an original DLL from the deployment package; and code to edit assembly code in the DLL to correspond to the unique instance.
11. The computer program product of claim 7 , in which the medium further comprises: code to generate source code corresponding to the unique instance for the DLL with a code generator; and code to compile the source code into the DLL with the code generator.
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.
13. The apparatus of claim 12 , in which the processor is further configured: to extract an original DLL from the deployment package; and to edit assembly code in the DLL to correspond to the unique instance.
14. The apparatus of claim 12 , in which the processor is further configured: to generate source code corresponding to the unique instance for the DLL with a code generator; and to compile the source code into the DLL with the code generator.
