Go to the PowerShell Browser located in the Object Browser Panel and press the Refresh button. Select the platform you wish the cache to rebuild in the Ribbon (Either 64 Bit or 32 Bit).Ģ.
Update the cache in PowerShell Studio 2012:ġ. You may need to restart PrimalScript 2012 in order to see the changes. In the Options window go to the Text Editor->PrimalSense category and press the “Clear Cache” button.ģ. Note: You need only update the cache in one application, since both products share the same cache information.Ģ.
Once the appropriate PowerShell controls are registered, you also need to update the PowerShell cache used by both applications. Note: The RegisterControls.exe updates both products, so you need only run it once. When the above window appears, check the relevant versions of PowerShell to register and press OK. This executable is located in the same directory as the application:Ĭ:\Program Files\SAPIEN Technologies, Inc\PrimalScript 2012\RegisterControls.exeĬ:\Program Files (x86)\SAPIEN Technologies, Inc\PowerShell Studio 2012\RegisterControls.exe This can be done by running RegisterControls.exe. Depending on if the correct PowerShell version was present when you initially installed the product, it might be necessary to re-register the controls. You will need to register the dependent PowerShell controls for the product. NOTE: In PowerShell Studio 4.2.89 and later, this step is done automatically. Step 1: Registering the dependent controls. Updating PrimalScript & PowerShell Studio: This article will also cover the case where you add a new module or snapin as well.
You can accomplish this by following the steps outlined below. This article addresses that very question. You upgraded your system to PowerShell 3.0, 4.0, or 5.0 and you want PrimalScript or PowerShell Studio to recognize the new version of PowerShell. Some of you may have already encountered this.
0 kommentar(er)
