Wanting to move away from WiseScript Editor
06/02/2017 1838 views
Here at my company I've been using WiseScript editor to create MSI wrappers for years now. I use InstallShield to create an MSI, but then I use a WiseScript to call the MSI and I use it heavily for pre and post installation purposes. WiseScript is dead according to everything that I've found online, but I'm having a hard time finding a replacement app that gives me the same features. Some say to use Powershell as a wrapper, but that still doesn't feel like the same features or ease of use for me. I'm also concerned with being able to manually just double-click and launch a .ps1 file if we ever need to manually launch an install on a user's station. Right now WiseScript creates an EXE so any admin can launch it. To my knowledge you have to launch a .ps1 with a specific command line in the appropriate execution policy is not configured on the station, which it's not at the moment. We currently use Symantec Management Platform as our method of application distribution.
I'm a self taught packager so I'm completely open to new ideas but I'm having a hard time finding the right place to guide me in the right direction for best practices. When I search for packaging best practices everything talks about creating the MSI. That's typically not a problem for me. I just have a hard time figuring out the pre/post installation tasks that I need to perform around the MSI. Maybe I'm just missing something. Thank you all for you help.
EDIT: Doing a bit more research. I'm curious if using a Powershell script to perform my pre/post installation work and then using something like IExpress.exe to create an EXE with my .ps1 and MSI would be a best practice? What do you guys think? Just to add more fun to my situation. I just learned that Powershell is not installed on XP station, of which about 1/2 of my environment is still at.