I need to create a msi package which reads from a configuration file(settings) and installs the package.
Please help me how to to create a msi package which reads configuration file at the time of install.
Thanks in advance.
You can pass custom parameters like this:
setup.msi /qb /l* log.txt WebSiteName=one PoolName=two
If you create your Setup package using Visual Studio then this shows how to pass parameters to custom install actions.
Visual Studio Setup - projects and custom actionsÂ
Related
I was trying to create windows .exe file to install moodle local plugin.
Is this doable installing plugin with .exe file?
Appreciate your suggestions. Reference to documentation access!
Are you trying to install Moodle? There are packages available for installing Moodle on a Windows machine:
https://docs.moodle.org/39/en/Complete_install_packages_for_Windows
Otherwise, using an exe to install a local plugin doesn't make any sense. You just need to copy the code to the local folder. Or unzip the code into a local folder.
Then either upgrade via your site yourmoodlesite/admin/ or use the command line:
php admin/cli/upgrade.php
See https://docs.moodle.org/39/en/Administration_via_command_line#Upgrading
I would like to add a custom script fragment to the unix uninstall script generated by install4j. This is possible for scripts available under the launchers tab. Is this also available for the uninstaller? I'm using install4j 6.0.4.
Yes you can.
If you want to run shell script you need before the uninstall file step (because your script will not longer will be on the filesystem).
If you want to run Java code you can do it after the files deletion:
Add in the Run script step add you Java code.
This omission will be fixed in install4j 7.0.7 where installer applications will have a "Custom script fragment" property.
Please contact support#ej-technologies.com to get a build where this is already implemented.
I have completed a project on VisualStudio and I have built the .exe file of this project. I wanted to make an installer that will include this .exe file as well as the postgreSQL and perl executable installers because my VB application relies on them to work. So I assume that if I want it to work properly on every windows-based PC I have to include those as well.
Is there a way I can include those 3 .exe(s) in a single setup (let's say .MSI file) and if yes what are the steps required to do so?
Thanks in advance!
Regards,
George.
An MSI shouldn't ever run an EXE installer. For that scenario you need what's called a bootstrapper / chainer. The two are similar except that boostrapper is things that must be installed before your MSI ( like Windows Installer itself ) and chainer are things that get installed along with your MSI.
InstallShield has two features for this. Setup / Feature Prerequisites and Suite Installers. Both can be used to chain together any number of EXE and MSI installers.
For more information see:
Using InstallShield 12 to Install .NET Framework 3.0
I am beginner in creating nuget packages. I created a nuget package which copies all files to solution explorer for now. I am trying to copy folder to users local folder where they have visual studio installed. Can I execute c# code while user installs nuget package on their visual studio solution? Any help would be highly appreciated.
You can add a powershell .ps1 script and set it to be executed while installing the nuget package. If Powershell wouldn't suffice ( most probably it would) and you absolutely want to have some piece of C# code run, just include the code in Powershell as described here: http://blogs.technet.com/b/stefan_gossner/archive/2010/05/07/using-csharp-c-code-in-powershell-scripts.aspx
I was trying to use Nuget as a software deployment system (repository, versioning and delivery) - idea from Octopus. Previously I was packaging ASP.NET sites into a self-extracting RAR archives with a .CMD startup scripts embeded. Now I'm trying to use Nuget creating puckages during automated build. The issue is that the package installation scripts (tools\Install.ps1 or tools\Init.ps1) do not execute if the package is being installed using command line:
nuget.exe install <package_id> -OutputDirectory <install_folder> -source <local_repo>
Same scripts are able to execute when package installed from Visual Studio Package Manager or Console.
I do not see why this shouldn't be possible given omnipresence of PowerShell.
Am I missing something or this is behaviour by design? Will appreciate you help.
Yes, we did consider MSDeploy but we already have install scripts that do the same thing and give more control and we need some strong package management and repository for build artifacts (something that Java folks do with Maven).
As of today, the powershell scripts are not invoked from doing installations from command line.
One reason for this is that, in general, most of the install/init actions are tied to dte and the visual studio project and doesn't add much value to be able to run it from outside VS.
We have a backlog item for enabling support for exe based scripts too in addition to powershell.