MegaBites-AI/Windows-powershell
0372
1<?xml version="1.0" encoding="utf-8"?>2<root>3 <!--4 Microsoft ResX Schema5 6 Version 2.07 8 The primary goals of this format is to allow a simple XML format9 that is mostly human readable. The generation and parsing of the10 various data types are done through the TypeConverter classes11 associated with the data types.12 13 Example:14 15 ... ado.net/XML headers & schema ...16 <resheader name="resmimetype">text/microsoft-resx</resheader>17 <resheader name="version">2.0</resheader>18 <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>19 <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>20 <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>21 <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>22 <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">23 <value>[base64 mime encoded serialized .NET Framework object]</value>24 </data>25 <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">26 <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>27 <comment>This is a comment</comment>28 </data>29 30 There are any number of "resheader" rows that contain simple31 name/value pairs.32 33 Each data row contains a name, and value. The row also contains a34 type or mimetype. Type corresponds to a .NET class that support35 text/value conversion through the TypeConverter architecture.36 Classes that don't support this are serialized and stored with the37 mimetype set.38 39 The mimetype is used for serialized objects, and tells the40 ResXResourceReader how to depersist the object. This is currently not41 extensible. For a given mimetype the value must be set accordingly:42 43 Note - application/x-microsoft.net.object.binary.base64 is the format44 that the ResXResourceWriter will generate, however the reader can45 read any of the formats listed below.46 47 mimetype: application/x-microsoft.net.object.binary.base6448 value : The object must be serialized with49 : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter50 : and then encoded with base64 encoding.51 52 mimetype: application/x-microsoft.net.object.soap.base6453 value : The object must be serialized with54 : System.Runtime.Serialization.Formatters.Soap.SoapFormatter55 : and then encoded with base64 encoding.56 57 mimetype: application/x-microsoft.net.object.bytearray.base6458 value : The object must be serialized into a byte array59 : using a System.ComponentModel.TypeConverter60 : and then encoded with base64 encoding.61 -->62 <xsd:schema id="root" xmlns="" xmlns:xsd="https://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">63 <xsd:import namespace="https://www.w3.org/XML/1998/namespace" />64 <xsd:element name="root" msdata:IsDataSet="true">65 <xsd:complexType>66 <xsd:choice maxOccurs="unbounded">67 <xsd:element name="metadata">68 <xsd:complexType>69 <xsd:sequence>70 <xsd:element name="value" type="xsd:string" minOccurs="0" />71 </xsd:sequence>72 <xsd:attribute name="name" use="required" type="xsd:string" />73 <xsd:attribute name="type" type="xsd:string" />74 <xsd:attribute name="mimetype" type="xsd:string" />75 <xsd:attribute ref="xml:space" />76 </xsd:complexType>77 </xsd:element>78 <xsd:element name="assembly">79 <xsd:complexType>80 <xsd:attribute name="alias" type="xsd:string" />81 <xsd:attribute name="name" type="xsd:string" />82 </xsd:complexType>83 </xsd:element>84 <xsd:element name="data">85 <xsd:complexType>86 <xsd:sequence>87 <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />88 <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />89 </xsd:sequence>90 <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />91 <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />92 <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />93 <xsd:attribute ref="xml:space" />94 </xsd:complexType>95 </xsd:element>96 <xsd:element name="resheader">97 <xsd:complexType>98 <xsd:sequence>99 <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />100 </xsd:sequence>101 <xsd:attribute name="name" type="xsd:string" use="required" />102 </xsd:complexType>103 </xsd:element>104 </xsd:choice>105 </xsd:complexType>106 </xsd:element>107 </xsd:schema>108 <resheader name="resmimetype">109 <value>text/microsoft-resx</value>110 </resheader>111 <resheader name="version">112 <value>2.0</value>113 </resheader>114 <resheader name="reader">115 <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>116 </resheader>117 <resheader name="writer">118 <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>119 </resheader>120 <data name="ShellBannerPowerShell" xml:space="preserve">121 <value>PowerShell {0}</value>122 </data>123 <data name="ShellBannerCLMode" xml:space="preserve">124 <value>[Constrained Language Mode]</value>125 </data>126 <data name="ShellBannerCLAuditMode" xml:space="preserve">127 <value>[Constrained Language AUDIT Mode : No Restrictions]</value>128 </data>129 <data name="ShellBannerNLMode" xml:space="preserve">130 <value>[No Language Mode]</value>131 </data>132 <data name="ShellBannerRLMode" xml:space="preserve">133 <value>[Restricted Language Mode]</value>134 </data>135 <data name="PreviewUpdateNotificationMessage" xml:space="preserve">136 <value> {1} A new PowerShell preview release is available: v{0} {2}137 {1} Upgrade now, or check out the release page at:{3}{2}138 {1} https://aka.ms/PowerShell-Release?tag=v{0} {4}{2}139</value>140 </data>141 <data name="StableUpdateNotificationMessage" xml:space="preserve">142 <value> {1} A new PowerShell stable release is available: v{0} {2}143 {1} Upgrade now, or check out the release page at:{3}{2}144 {1} https://aka.ms/PowerShell-Release?tag=v{0} {4}{2}145</value>146 </data>147 <data name="LTSUpdateNotificationMessage" xml:space="preserve">148 <value> {1} A new PowerShell LTS release is available: v{0} {2}149 {1} Upgrade now, or check out the release page at:{3}{2}150 {1} https://aka.ms/PowerShell-Release?tag=v{0} {4}{2}151</value>152 </data>153 <data name="UsageHelp" xml:space="preserve">154 <value>Usage: pwsh[.exe] [-Login] [[-File] <filePath> [args]]155 [-Command { - | <script-block> [-args <arg-array>]156 | <string> [<CommandParameters>] } ]157 [-CommandWithArgs <string> [<CommandParameters>]158 [-ConfigurationName <string>] [-ConfigurationFile <filePath>]159 [-CustomPipeName <string>] [-EncodedCommand <Base64EncodedCommand>]160 [-ExecutionPolicy <ExecutionPolicy>] [-InputFormat {Text | XML}]161 [-Interactive] [-MTA] [-NoExit] [-NoLogo] [-NonInteractive] [-NoProfile]162 [-NoProfileLoadTime] [-OutputFormat {Text | XML}]163 [-SettingsFile <filePath>] [-SSHServerMode] [-STA]164 [-Version] [-WindowStyle <style>]165 [-WorkingDirectory <directoryPath>]166 167 pwsh[.exe] -h | -Help | -? | /?168 169PowerShell Online Help https://aka.ms/powershell-docs170 171All parameters are case-insensitive.</value>172 </data>173 <data name="ExtendedHelp" xml:space="preserve">174 <value>175 176-File | -f177 178 If the value of File is "-", the command text is read from standard input.179 Running "pwsh -File -" without redirected standard input starts a regular180 session. This is the same as not specifying the File parameter at all.181 182 This is the default parameter if no parameters are present but values are183 present in the command line. The specified script runs in the local scope184 ("dot-sourced"), so that the functions and variables that the script185 creates are available in the current session. Enter the script file path186 and any parameters. File must be the last parameter in the command, because187 all characters typed after the File parameter name are interpreted as the188 script file path followed by the script parameters.189 190 Typically, the switch parameters of a script are either included or191 omitted. For example, the following command uses the All parameter of the192 Get-Script.ps1 script file: "-File .\Get-Script.ps1 -All"193 194 In rare cases, you might need to provide a BOOLEAN value for a switch195 parameter. To provide a BOOLEAN value for a switch parameter in the value196 of the FILE parameter, Use the parameter normally followed immediately by a197 colon and the boolean value, such as the following:198 "-File .\Get-Script.ps1 -All:$False".199 200 Parameters passed to the script are passed as literal strings, after201 interpretation by the current shell. For example, if you are in cmd.exe and202 want to pass an environment variable value, you would use the cmd.exe203 syntax: "pwsh -File .\test.ps1 -TestParam %windir%"204 205 In contrast, running "pwsh -File .\test.ps1 -TestParam $env:windir" in206 cmd.exe results in the script receiving the literal string "$env:windir"207 because it has no special meaning to the current cmd.exe shell. The208 "$env:windir" style of environment variable reference can be used inside a209 Command parameter, since there it is interpreted as PowerShell code.210 211 Similarly, if you want to execute the same command from a Batch script,212 you would use "%~dp0" instead of ".\" or "$PSScriptRoot" to represent the current213 execution directory: "pwsh -File %~dp0test.ps1 -TestParam %windir%". If you214 instead used ".\test.ps1", PowerShell would throw an error because it cannot215 find the literal path ".\test.ps1".216 217 When the script file invoked terminates with an exit command, the process218 exit code is set to the numeric argument used with the exit command. With219 normal termination, the exit code is always 0.220 221 Similar to -Command, when a script-terminating error occurs, the exit code222 is set to 1. However, unlike with -Command, when the execution is223 interrupted with Ctrl-C the exit code is 0.224 225-Command | -c226 227 Executes the specified commands (and any parameters) as though they were228 typed at the PowerShell command prompt, and then exits, unless the NoExit229 parameter is specified.230 231 The value of Command can be "-", a script block, or a string. If the value232 of Command is "-", the command text is read from standard input.233 234 The Command parameter only accepts a script block for execution when it can235 recognize the value passed to Command as a ScriptBlock type. This is only236 possible when running pwsh from another PowerShell host. The ScriptBlock237 type may be contained in an existing variable, returned from an expression,238 or parsed by the PowerShell host as a literal script block enclosed in239 curly braces "{}", before being passed to pwsh.240 241 pwsh -Command {Get-WinEvent -LogName security}242 243 In cmd.exe, there is no such thing as a script block (or ScriptBlock type),244 so the value passed to Command will always be a string. You can write a245 script block inside the string, but instead of being executed it will246 behave exactly as though you typed it at a typical PowerShell prompt,247 printing the contents of the script block back out to you.248 249 A string passed to Command is still executed as PowerShell script, so the250 script block curly braces are often not required in the first place when251 running from cmd.exe. To execute an inline script block defined inside a252 string, the call operator "&" can be used:253 254 pwsh -Command "& {Get-WinEvent -LogName security}"255 256 If the value of Command is a string, Command must be the last parameter for257 pwsh, because all arguments following it are interpreted as part of the258 command to execute.259 260 When called from within an existing PowerShell session, the results are261 returned to the parent shell as deserialized XML objects, not live objects.262 For other shells, the results are returned as strings.263 264 If the value of Command is "-", the command text is read from standard265 input. You must redirect standard input when using the Command parameter266 with standard input. For example:267 268 @'269 "in"270 271 "hi" |272 % { "$_ there" }273 274 "out"275 '@ | powershell -NoProfile -Command -276 277 This example produces the following output:278 279 in280 hi there281 out282 283 The process exit code is determined by status of the last (executed)284 command within the script block. The exit code is 0 when $? is $true or 1285 when $? is $false. If the last command is an external program or a286 PowerShell script that explicitly sets an exit code other than 0 or 1, that287 exit code is converted to 1 for process exit code. To preserve the specific288 exit code, add exit $LASTEXITCODE to your command string or script block.289 290 Similarly, the value 1 is returned when a script-terminating291 (runspace-terminating) error, such as a throw or -ErrorAction Stop, occurs292 or when execution is interrupted with Ctrl-C.293 294-CommandWithArgs | -cwa295 296 [Experimental]297 Executes a PowerShell command with arguments. Unlike `-Command`, this298 parameter populates the `$args built-in variable which can be used by the299 command.300 301 The first string is the command and subsequent strings delimited by whitespace302 are the arguments.303 304 For example:305 306 pwsh -CommandWithArgs '$args | % { "arg: $_" }' arg1 arg2307 308 This example produces the following output:309 310 arg: arg1311 arg: arg2312 313-ConfigurationName | -config314 315 Specifies a configuration endpoint in which PowerShell is run. This can be316 any endpoint registered on the local machine including the default317 PowerShell remoting endpoints or a custom endpoint having specific user318 role capabilities.319 320 Example: "pwsh -ConfigurationName AdminRoles"321 322-ConfigurationFile323 324 Specifies a session configuration (.pssc) file path. The configuration325 contained in the configuration file will be applied to the PowerShell326 session.327 328 Example: "pwsh -ConfigurationFile "C:\ProgramData\PowerShell\MyConfig.pssc"329 330-CustomPipeName331 332 Specifies the name to use for an additional IPC server (named pipe) used333 for debugging and other cross-process communication. This offers a334 predictable mechanism for connecting to other PowerShell instances.335 Typically used with the CustomPipeName parameter on "Enter-PSHostProcess".336 337 This parameter was introduced in PowerShell 6.2.338 339 For example:340 341 # PowerShell instance 1342 pwsh -CustomPipeName mydebugpipe343 # PowerShell instance 2344 Enter-PSHostProcess -CustomPipeName mydebugpipe345 346-EncodedCommand | -e | -ec347 348 Accepts a Base64-encoded string version of a command. Use this parameter to349 submit commands to PowerShell that require complex, nested quoting. The350 Base64 representation must be a UTF-16 encoded string.351 352 For example:353 354 $command = 'dir "c:\program files" '355 $bytes = [System.Text.Encoding]::Unicode.GetBytes($command)356 $encodedCommand = [Convert]::ToBase64String($bytes)357 pwsh -encodedcommand $encodedCommand358 359-ExecutionPolicy | -ex | -ep360 361 Sets the default execution policy for the current session and saves it in362 the $env:PSExecutionPolicyPreference environment variable. This parameter363 does not change the persistently configured execution policies.364 365 This parameter only applies to Windows computers. The366 $env:PSExecutionPolicyPreference environment variable does not exist on367 non-Windows platforms.368 369-InputFormat | -inp | -if370 371 Describes the format of data sent to PowerShell. Valid values are "Text"372 (text strings) or "XML" (serialized CLIXML format).373 374-Interactive | -i375 376 Present an interactive prompt to the user. Inverse for NonInteractive377 parameter.378 379-Login | -l380 381 On Linux and macOS, starts PowerShell as a login shell, using /bin/sh to382 execute login profiles such as /etc/profile and ~/.profile. On Windows,383 this switch does nothing.384 385 [!IMPORTANT] This parameter must come first to start PowerShell as a login386 shell. The parameter is ignored if passed in any other position.387 388 To set up pwsh as the login shell on UNIX-like operating systems:389 390 - Verify that the full absolute path to pwsh is listed under /etc/shells391 392 - This path is usually something like /usr/bin/pwsh on Linux or393 /usr/local/bin/pwsh on macOS394 - With some installation methods, this entry will be added395 automatically at installation time396 - If pwsh is not present in /etc/shells, use an editor to append the397 path to pwsh on the last line. This requires elevated privileges to398 edit.399 400 - Use the chsh utility to set your current user's shell to pwsh:401 402 chsh -s /usr/bin/pwsh403 404 [!WARNING] Setting pwsh as the login shell is currently not supported on405 Windows Subsystem for Linux (WSL), and attempting to set pwsh as the406 login shell there may lead to being unable to start WSL interactively.407 408-MTA409 410 Start PowerShell using a multi-threaded apartment. This switch is only411 available on Windows.412 413-NoExit | -noe414 415 Does not exit after running startup commands.416 417 Example: "pwsh -NoExit -Command Get-Date"418 419-NoLogo | -nol420 421 Hides the banner text at startup of interactive sessions.422 423-NonInteractive | -noni424 425 This switch is used to create sessions that shouldn't require user input.426 This is useful for scripts that run in scheduled tasks or CI/CD pipelines.427 Any attempts to use interactive features, like 'Read-Host' or confirmation428 prompts, result in statement terminating errors rather than hanging.429 430-NoProfile | -nop431 432 Does not load the PowerShell profiles.433 434-NoProfileLoadTime435 436 Hides the PowerShell profile load time text shown at startup when the load437 time exceeds 500 milliseconds.438 439-OutputFormat | -o | -of440 441 Determines how output from PowerShell is formatted. Valid values are "Text"442 (text strings) or "XML" (serialized CLIXML format).443 444 Example: "pwsh -o XML -c Get-Date"445 446 When called within a PowerShell session, you get deserialized objects as447 output rather plain strings. When called from other shells, the output is448 string data formatted as CLIXML text.449 450-SettingsFile | -settings451 452 Overrides the system-wide "powershell.config.json" settings file for the453 session. By default, system-wide settings are read from the454 "powershell.config.json" in the "$PSHOME" directory.455 456 Note that these settings are not used by the endpoint specified by the457 "-ConfigurationName" argument.458 459 Example: "pwsh -SettingsFile c:\myproject\powershell.config.json"460 461-SSHServerMode | -sshs462 463 Used in sshd_config for running PowerShell as an SSH subsystem. It is not464 intended or supported for any other use.465 466-STA467 468 Start PowerShell using a single-threaded apartment. This is the default.469 This switch is only available on Windows.470 471-Version | -v472 473 Displays the version of PowerShell. Additional parameters are ignored.474 475-WindowStyle | -w476 477 Sets the window style for the session. Valid values are Normal, Minimized,478 Maximized, and Hidden.479 480-WorkingDirectory | -wd481 482 Sets the initial working directory by executing at startup. Any valid483 PowerShell file path is supported.484 485 To start PowerShell in your home directory, use: pwsh -WorkingDirectory ~486 487-Help, -?, /?488 489 Displays help for pwsh. If you are typing a pwsh command in PowerShell,490 prepend the command parameters with a hyphen (-), not a forward slash (/).491 </value>492 </data>493</root>494