So far we introduced you to the PrimalScript 2012 Ribbon interface and the first 4 categories in the Home tab. Today we take a closer look at the remaining 4 items.
The platform selector lets you choose between 32 and 64 bit, provided you are running a 64 bit operating system. Otherwise it is quite obviously nailed to 32 bit and won’t do anything. It determines the platform you want to use for executing and debugging scripts. So if you have 32 bit VBScripts and 64 bit PowerShell script, here is where you change the target.
STA (Single Thread Apartment) mode refers to a special threading model PowerShell scripts must use when employing certain controls. WPF controls are a prime example where pushing this button is required. This mode has no effect on any other language but PowerShell.
Elevation refers to the split administrative account model on Windows Vista and above. Even when you are logged on as a user who is a member of the local administrators group, you still need to execute certain operations elevated or they will fail. So if your script does something that requires elevation, for example copying files to the Program Files folder, this should be set when executing your script. If you have disabled UAC (User Access Control) this obviously has no effect.
This is where it all happens. Here you run your scripts locally and remotely, sign them and package them.
Run includes options to run your script elevated, in a shell, run just the selection or run it with arguments. In the previous section you saw he elevation button which makes it easy to switch this on if most or all your scripts require administrative access. If this is only an occasional thing you have an option on the Run menu here.
Remoting can be done with RSEE against a single computer or a list of machines. If you use PowerShell, you can also use Windows remoting.
The packaging button just packages your currently active script, while the menu has the three options shown below.
It’s pretty straight forward so we are just going to let you play with that.
The PrimalScript 2012 Debugger is an evolution of the 2011 version. There some additional features we will discuss later. Most of these buttons are the same as the ones on PrimalScript 2011’s debug toolbar. The TracePoint button is new, but we will also discuss this one later.
Last but not least, let’s get some help. The Help button takes the current word and hands it to the SAPIEN Document Explorer to look it up. Search online just googles the current word and Ask the experts will take you to our community site www.scriptinganswers.com
So that concludes the introduction to the Home tab. In our next post we will look at the application menu. We designated it as Files menu because that’s what it deals with and what we are all used to.