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="Utf7EncodingObsolete" xml:space="preserve">121 <value>Encoding 'UTF-7' is obsolete, please use UTF-8.</value>122 </data>123 <data name="UtilityFileExistsNoClobber" xml:space="preserve">124 <value>File {0} already exists and {1} was specified.</value>125 </data>126 <data name="OutFile_ReadWriteFileNotFileSystemProvider" xml:space="preserve">127 <value>Cannot open file because the current provider ({0}) cannot open a file.</value>128 </data>129 <data name="OutFile_MultipleFilesNotSupported" xml:space="preserve">130 <value>Cannot perform operation because the path resolved to more than one file. This command cannot operate on multiple files.</value>131 </data>132 <data name="OutFile_DidNotResolveFile" xml:space="preserve">133 <value>Cannot perform operation because the wildcard path {0} did not resolve to a file.</value>134 </data>135 <data name="OutFile_WriteToFileEncodingUnknown" xml:space="preserve">136 <value>Unknown encoding {0}; valid values are {1}.</value>137 </data>138 <data name="ExportPSSession_ErrorDirectoryExists" xml:space="preserve">139 <value>The directory '{0}' already exists. Use the -Force parameter if you want to overwrite the directory and files within the directory.</value>140 </data>141 <data name="ExportPSSession_ErrorModuleNameOrPath" xml:space="preserve">142 <value>The user module path does not exist, and hence a module folder cannot be created for the provided module name '{0}'.</value>143 </data>144 <data name="ExportPSSession_CannotCreateOutputDirectory" xml:space="preserve">145 <value>Cannot create the module {0} due to the following: {1}. Use a different argument for the -OutputModule parameter and retry.</value>146 <comment>{StrContains="OutputModule"}147{0} is a placeholder for the name of a directory148{1} is a placeholder for an error message from the inner exception149 150Reviewed by TArcher on 2010-07-21151 152Example usage:153PS C:\> $s = New-PSSession154PS C:\> Export-PSSession -Session $s -OutputModule gibberish:here155Export-PSSession : Cannot create the module 'gibberish:here' due to the following: Cannot find drive. A drive with the name 'gibberish' does not exist. Use a different argument for the -OutputModule parameter and try again.156At line:1 char:1157+ Export-PSSession -Session $s -OutputModule gibberish:here158+ ^159 + CategoryInfo : ResourceExists: (gibberish:here:String) [Export-PSSession], ArgumentException160 + FullyQualifiedErrorId : ExportProxyCommand_CannotCreateOutputDirectory,Microsoft.PowerShell.Commands.ExportPSSessionCommand161 </comment>162 </data>163 <data name="ExportPSSession_ScriptGeneratorVersionMismatch" xml:space="preserve">164 <value>The module cannot be loaded because it has been generated with an incompatible version of the {0} cmdlet. Generate the module with the {0} cmdlet from the current session, and try loading the module again.</value>165 </data>166</root>167