Posts Tagged ‘MSI’


 

Distributing files with your packaged scripts

Tuesday, March 22nd, 2016 by Alex Riedel
We get this question every week: Why can I not include my data files, secondary scripts, modules, other executables etc. with the packaged executable and have it unpack them when I run it? If you have been a SAPIEN customer for a few years you may remember that we had this feature in the packager until the 2012 version. The predominant operating system at the time was Windows XP and this worked fine. With the advent of Windows Vista and Windows 7 we received this question more and more: “Why does my packaged script no longer work?. You need…   More »

PrimalScript 2014 Service build 7.0.49

Tuesday, October 14th, 2014 by Alex Riedel
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…   More »

From script to server – Deploying solutions with PrimalScript 2014 (Part 4)

Monday, April 21st, 2014 by Alex Riedel
Welcome back. As we previously discussed, PrimalScript 2014 has a few new options for the script packager and has added features for creating MSI databases and deploying your script solutions. If you have missed the previous three installments, use the links below to catch up. From script to server – Deploying solutions with PrimalScript 2014 (Part 1) From script to server – Deploying solutions with PrimalScript 2014 (Part 2) From script to server – Deploying solutions with PrimalScript 2014 (Part 3) Today we are putting this all together and show you how to use this efficiently in your day-to-day operations.…   More »

From script to server – Deploying solutions with PrimalScript 2014 (Part 3)

Monday, April 14th, 2014 by Alex Riedel
The last time we looked at the new installer option in PrimalScript 2014. You can find the article here: http://www.sapien.com/blog/2014/04/07/from-script-to-server-deploying-solutions-with-primalscript-2014-part-2 If you look at the deploy tab again, you will see a “Deployment” group. These functions will help you distribute your solutions to your target audience.   First lets look at the settings. There are two items that are mandatory. You need to have at least one file that gets deployed. If you look at the combobox, there are three items in it: Depending on what else you have defined for your solution, the initial file to deploy can either…   More »

From script to server – Deploying solutions with PrimalScript 2014 (Part 2)

Monday, April 7th, 2014 by Alex Riedel
Last time we looked at the new packager options in PrimalScript 2014. You can find the article here: http://www.sapien.com/blog/2014/03/25/from-script-to-server-deploying-solutions-with-primalscript-2014-part-1 If you look at the deploy tab again, you see an installer group that was not an option in any of the previous PrimalScript versions This new feature allows you to wrap your scripts, packaged executables, associated scripts, modules, configuration and binary files in a proper Microsoft Windows Installer database for easier deployment. If you have participated in our MSIWizard community preview you may already be familiar with a lot of this. Let’s examine the options we have. Most of the…   More »

From script to server – Deploying solutions with PrimalScript 2014 (Part 1)

Tuesday, March 25th, 2014 by Alex Riedel
If you take a look at the new 2014 version of PrimalScript you will discover a new tab on the ribbon interface: “Deploy” This tab combines three major stepping stones for deploying your scripting solutions: 1. The Script Packager that you all know from previous versions of PrimalScript. Of course this wouldn’t be much of a new version if there weren’t any upgrades. 2. The new MSI builder, which allows you to take your scripts, packages, modules and all the supplemental files you may need and wrap them into a professional grade installer package. 3. Last but not least PrimalScript’s…   More »

Introducing the MSI Wizard

Wednesday, June 5th, 2013 by Alex Riedel
Both PrimalScript 2014 and PowerShell Studio 2014 will have to ability to create Windows Installer files (MSI) for your scripts, modules or packaged executables. It works pretty straightforward; put the files you want to install into a folder, enter some additional settings and mucho presto you have an installer. As we previously pointed out, this may be a transition for some of you. So we decided to make a time limited preview copy available for everyone to test. Let’s go through the fields and options. 1. Product Details Product Name: That is what you will see in the Control Panel’s…   More »

Changes are coming to the script packager

Monday, June 3rd, 2013 by Alex Riedel
The Script Packager has been a key feature of PrimalScript for many years now. Devised originally in the Windows 2000 era, it has some features that simply are no longer relevant or applicable in modern Windows versions. As many of you know, the packager has the ability to self-extract data files and COM objects when invoked. In that regard, packages work very much like a self-extracting ZIP files. Obviously that method did impose some size limitations, but it has worked well for many years. Starting with Windows Vista and Windows Server 2008, this self-extracting nature of script packages became more…   More »

Installer change for PrimalScript 2009

Sunday, November 29th, 2009 by Alex Riedel
PrimalScript has a long history of using InstallShield installers (since version 1.0). Having used one installer product since 1997 creates quite a history, so making a change was not an easy decision. With the next service build (5.0.621) PrimalScript 2009 will start to use the same Advanced Installer that all other SAPIEN products are currently using. The reasons for this are plenty, but the main reason is that this tool allows us to create a more streamlined and error-free upgrade experience for existing installations. We have done everything we can to make this transition as smooth and effortless as possible,…   More »