![]() To shed more light on MSIs, many competitive/non-competitive platforms are providing MSI distributions to meet the need for scalable/secure distribution methods. From an external point of view, the conversion methods seem lightweight to complete and add more availability to your product and its adoption/safe use. Taking a step back at the full scope of this common request sheds light on the possibility of an identified need/growth of the product distribution method that does not seem to be extensive to add, per the provided research, to the product dev pipeline distribution. Again, I only mention this as constructive criticism and you can take it how you’d like however, I only mean to assist in the progress of the community platform and this request. I have, on several occasions, had to step back, take a breath, and reapproach similarly IT support requests/questions. ![]() I get the frustration of a talked-at post which it seems this started as I would find a one-sentence “command” demeaning for sure. Not to be too sensitive here, but the tone of your response was very standoffish, and it seems the person might not have English as their first language (blind assumption from sentence structure). It kind of puts a harmful pretense of wanting to post anything productive or constructive to a cohort that, in nature, should be positive for growth. If you see an uptick in a request for something, compile some supporting research (which you did eventually) when responding to a request, and try not to immediately demean/negatively challenge someone directly in a communal format. Respectfully, I’ll try not to make this personal, but I would like to provide some constructive criticism if you’d be welcome. Much love on this as a former developer myself as well. ![]() It also would not invalidate the fingerprint provided (GPG Finger Print) due to the lack of file manipulation/conversion needed to make it easier to manage the product through the reasons mentioned above by BTW, the Data Security professional in me sincerely thanks you for providing the validation keys on such a highly requested tool in the IT/DevOps sector. To directly answer your question, providing an MSI puts less overhead on IT professionals and Orgs with teams using the product to make it easier to digest and distribute in mass. I hope this explains why IT-professionals ask for As has pointed out, providing an MSI allows endpoint management to be streamlined and automated with efficiencies for distributing requested software for DevOps teams and the like. With a MSI file we can easy do a silent install, we can repair the software using built in MSI solutions, uninstall silently, version controll, have a log file created and modify settings like disable automatic updates using a Transform file (as it’s something organisations do not want to have enabled as users usually do not have admin access to the local computer and therefor can’t install any updates to the program).Ī MSI-file can also easily be converted to a file format compatible with Intune distribution (Microsoft offeres free software for converting). The best solution is off cause if a MSI-file is offered from the creator. Template exe should pass all command line arguments to msiexec as if msiexec is launched directly.The main reason a MSI file is asked for is that they are used when distributing software using a deployment solutions in an organisation, most commonly Microsoft SCCM or deploying software using ActiveDirectory.įor example, I repackage software that do not offer a MSI file so that I can distribut them within my organisation by running the installer and a repackage software that analyse what changes the installer makes to the system and then compile those changes to a MSI-file. Suggested solution is to wrap msi installer created with WiX into an exe file.Ī template exe file with a placeholder for msi file in its resources will be compiled and embedded in jpackage at JDK build.Īt run-time, when jpackage is requested to produce exe installer, it will produce msi installer and insert it at msi placeholder of the template exe.įunctionality of template exe will be to extract msi file from resources into a temporary directory and run msiexec on it. However with Innor Setup removed exe installers will still be supported. Reduce dependencies on 3rd party tools. Simplify creation of custom actions in installers. Ĭonsiderations to have only one 3rd party tool to build installers: Primary reason to prefer WiX over Inno Setup is that Inno Setup doesn't produce Windows Installer compatible installation packages while WiX does. The suggestion is to get rid of Inno Setup. Support for two different tools producing installers for one platform (Windows) doesn't look like an optimized approach. msi installers and Inno Setup to produce. Jpackage supports two types of installers for Windows platform.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |