We do not always blog about service builds.
But when we do, it is important.
Code responsibly.
PrimalScript 2014 has some new features in the MSI builder you want to check out.
First of all you can now control the specific minimum version of PowerShell required. If an older version is present, a message box will inform the user and the install is aborted.
You see PowerShell V5 there in preparation for its release, but please note that V5 is not released and not supported. You should not ever use pre-release software in a production environment.
The second new feature gives you more control over the installed folder structure.
If you leave the field highlighted in the screenshot above empty your installer is built as before. The underlying Wix toolset still uses a staging folder, but we create that temporarily and you never see that.
Now if you specify a folder there, e.g. ‘C:\Users\Alex\Documents\SAPIEN\Scripts\Notepad runner staging folder”, PrimalScript will copy all the files specified in the list above to that folder. That makes sure they will always be updated with the latest version.
Let’s just assume your PowerShell application needs some additional files and you want them neatly organized in folders. As shown above, you just create the folders you need in the specified staging area and copy whatever files you need there. It is really that easy. Build the installer and run it.
As you can see, the files you prepared in the staging folder made it to the final install folder.
Aside from the MSI features we also added some improvements for our friends using Winbatch. Code folding on a function/subroutine level is no supported and backtics are now recognized as string delimiters.
As always, we are working on new features all the time, but if you need something or a specific item is of huge importance, drop us a note in the wish list forum.
