STA mode is not something you normally have to consider when writing scripts, but it is something that you should be aware of if you are creating GUIs tools. Note: The PowerShell ISE always runs in STA mode. If you are using PowerShell V2, you will have to tell the console to run under STA mode by using the following parameter: Starting with PowerShell V3 the console runs using STA mode as the default. TIP: If you add the following comment to your script, PowerShell Studio and PrimalScript will force the script to run in STA mode: # %ForceSTA% = True Key Features PowerShell Script Editor Features a. In addition, you will need to make sure your ps1 scripts require STA when running. PowerShell Studio keeps manifest maintenance to a minimum by auto-exporting functions and ps1xml files. But when you package a script, be sure to retain the STA mode settings. Luckily, PowerShell Studio detects when you have a STA mode dependent control and will force the GUI form to run in STA mode. If you use the Clipboard static methods, then you will need to use STA mode: :: SetText( "Paste this text to the clipboard" ) STA Mode is required if you use Ctrl + C to copy text of the cells.
STA Mode is required if you use AutoCompleteSource.
STA Mode is required if you use AutoCompleteSource The following controls will function without STA, but if you use certain features, STA mode will be required: TextBox The following controls require STA otherwise they will not appear: FileBrowserDialog I will not go into the details but you need not contain yourself with the inner workings of COM objects, other than the fact that STA is required for some of the GUI controls to function correctly. STA (Single Threaded Apartment) and MTA (Multi-Threaded Apartment) have to do with how a process manages legacy COM objects and their communications between multiple threads. Recently on our forums, a user asked why certain controls didn’t function correctly or threw an error when he unchecked the STA option in PowerShell Studio.
0 kommentar(er)
