This is a major headache for every network administrators who are often required to push unattended remote software installation and uninstallation and are responsible for software infrastructure of an organisation. Thus, two installers, created by two different creation tools, namely Wise Studio and InstallSheild will have everything different. Depending on the creation tool used, an EXE installation might have different customised options for installation and uninstallation, error handling process and deployment method.Īs there are no single standard for EXE installation, different vendors use different set of standards to create their own executables. EXE files, on the other hand, are just executable files which don’t adhere to any defined standard. This means that all the MSI packages which are created using different packaging tools have similar deployment and management system. MSI packages are created according to the standard definition created by the Windows Installer Technology from Microsoft. However, in this case the question was about the difference in size between the EXE and the MSI coming out of an InstallAware build, and then the difference is the runtimes explained above.MSI packaging is considered to be the future of application packaging and Microsoft encourages software developers and administrators to reformat the EXE packages to MSI packages. Legacy Setup.exe Installer: Note that an EXE file can also be a non-MSI installer In other words an old-style installer not based on the Microsoft MSI format (which is a MS-SQL database stored in an office-style binary file), but rather an installation script of various formats such as Wise Script, Installscript, Inno Setup, NSIS, etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |