I have created dummy MSI using wix and used APPDIR property with one folder path for installed location .I imported this msi in to install shield and installation got success via install shield installer but I want to change the APPDIR value through install shield installer UI . Please give me the right way to proceed in install shield .How to interact with msi in installed?
If you're calling the MSI directly from the command line it is just a matter of adding PROPERTY=VALUE on the command line after the install switches. If you're calling the InstallShield bootstrapper (setup.exe) then you'll have to wrap it in a /v switch.
Related
The WIX environment variable does not point to an install of the WiX Toolset.
Current value: WindowsPath('.')
While creating briefcase in BeeWare, you should have admin access because it downloads and install packages.
This issue is coming because briefcase is unable to download Wix Toolset and unable to point out Wix environment variable.
You can manually download Wix Toolset from here https://wixtoolset.org/releases/
install it and check your environment variables in system variables you can find Wix.
Now try to create briefcase after installation.
Close the terminal you're working on.
Install WIX toolkit form https://wixtoolset.org/
Install via GUI installer.
Make sure it has been added to your system variable path. (refer picture below)
Run briefcase create.
Hope this helps :)
I want to know whether it is possible to create setup.exe (64-bit) from install shield.
I have read following things to do this, but nothing worked :
https://community.flexera.com/t5/InstallShield-Forum/64-bit-Setup-Isntallation/m-p/55761#M33183
http://www.installationdeveloper.com/2169/how-to-create-a-pure-64-bit-installation-in-installshield/
Actually I'm not able to load the 64-bit dll into 32-bit installer(using UseDLL() ), following is the reason for that, so I want to build 64-bit setup.exe, which might load my 64-bit dll.
https://community.flexera.com/t5/InstallShield-Knowledge/Can-I-Load-64-bit-DLL-Files-in-InstallScript/ta-p/3819
Thanks in advance.
UseDLL is part of InstallScript. InstallShield Installscript engine supports only 32 bit dlls as of now. So, UseDLL does not load x64 DLLs.
Install Script Project is still 32-bit(in Install Shield 2020), They are supporting MSI project as 64-bit (from Install Shield 2020). So we can not build installer as 64-bit from Installer script Project.
I have a msi installer created on windows, I put the msi into linux platform and I use 7z to extract content of msi installer, after that I used lcab command for extract and change some files, also using lcab command I put all files that I modified into cab. Now I need to restore msi, any idea?
You can use msi-packager.
Can be installed on Ubuntu/Debian using:
sudo apt-get install msitools nodejs npm
sudo npm install -g msi-packager
https://www.npmjs.com/package/msi-packager
Here is the full procedure to manipulate MSI files under Linux. The idea is export the MSI content to XML, modify the XML and then repack de MSI file, you can modify even the EXE files, not only tables:
Install WINE 32 bits version
Install WineTricks, you need it for DLL and frameworks installation.
Install .NET2.0, .NET4.0, MSXML6, VCRUN6 with winetricks (easy as ./winetricks dotnet20 dotnet40 msxml6 vcrun6)
Download MSI2XML & XML2MSI executables from the [official project page(https://msi2xml.sourceforge.io/)
Execute wine msi2xml installer.msi
Edit the XML file, then, pack again with wine xml2msi installer.xml
You are done, here is your MSI file!
Hope that helps, with MSI2XML & XML2MSI you can manipulate MSI files under Windows but also under Linux with WINE and it's 100% working solution.
I have easily installed Node.js before on Macs and other PCs, but the PC I have now at work restricts the running of .msi files.
Is there a way to manually install and configure node.js and npm on Windows 7? I have access to Powershell.
Installing nodejs (and npm) on a Windows 7 machine does not require any "magic" if you have Admin access on the target machine and do not care about setting up the expected "uninstall", various Windows performance counters, event tracing or Start menu entries.
To manually install from an existing installation on one machine to another machine, simply
Copy the entire contents of your "\Program Files\nodejs" and "\Users\USERNAME\AppData\Roaming\npm" directories as well as the "\Users\USERNAME\.npmrc" file to the same directories on target machine. (Replace USERNAME with your own Windows login name.)
Edit the "\Users\USERNAME\.npmrc" file to replace the source username with the username on the target machine.
Add "C:\Program Files\nodejs" and "C:\Users\USERNAME\AppData\Roaming\npm" to your PATH.
If you'd like to manually install direct from the MSI (without an existing installation to work from), get Scott Willeke's excellent lessmsi program, which allows you to extract all the files from any msi archive and discover all the actions taken by the Windows Installer, such as required edits to the Register, etc. (Though for nodejs, you'll only need to edit the Registry to add the proper keys to uninstall it automagically.)
I am using InstallShield Express Spring 2012 SP1. I would like to run the SQLLocalDb_x64.MSI from a custom action.
Is it possible to run an MSI from a custom action in InstallShield Express?
As a general rule, you cannot run an MSI as a custom action on Install Execute Sequence in another main MSI package. Windows Installer does not allow two MSI packages to run at the same time, so you will get an error message.
The standard approach for launching an MSI conditionally from another MSI is to embed it as a chained package.
Unfortunately I don't use InstallShield Express, so I don't know if it supports chained packages, usually this feature is available in a commercial edition.
I am fully agree with Bogdan, but there is one trick. You can run msi from custom action at the end of your installation after InstallFinalize phase. You could use the following CA: InstallIntStd 226 SystemFolder msiexec.exe /passive /i "[SOURCEDIR]YourSetup.msi"
Where:
InstallIntStd name of custom action;
226 Type: An asynchronous execution of EXE without waiting result;
SystemFolder Directory where msiexec located;
msiexec.exe /passive /i "[SOURCEDIR]YourSetup.msi" Launch string.