Dongbo Wang
GitHub
commit
fe38bc76d6
|
|
@ -11,7 +11,7 @@ DuplicatePathFoundError=The input to {0} parameter contains a duplicate path '{1
|
|||
ArchiveFileIsEmpty=The archive file {0} is empty.
|
||||
CompressProgressBarText=The archive file '{0}' creation is in progress...
|
||||
ExpandProgressBarText=The archive file '{0}' expansion is in progress...
|
||||
AppendArchiveFileExtensionMessage=The archive file path '{0}' supplied to the DestinationPath patameter does not include .zip extension. Hence .zip is appended to the supplied DestinationPath path and the archive file would be created at '{1}'.
|
||||
AppendArchiveFileExtensionMessage=The archive file path '{0}' supplied to the DestinationPath parameter does not include .zip extension. Hence .zip is appended to the supplied DestinationPath path and the archive file would be created at '{1}'.
|
||||
AddItemtoArchiveFile=Adding '{0}'.
|
||||
CreateFileAtExpandedPath=Created '{0}'.
|
||||
InvalidArchiveFilePathError=The archive file path '{0}' specified as input to the {1} parameter is resolving to multiple file system paths. Provide a unique path to the {2} parameter where the archive file has to be created.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@
|
|||
ArchiveFileIsEmpty=The archive file {0} is empty.
|
||||
CompressProgressBarText=The archive file '{0}' creation is in progress...
|
||||
ExpandProgressBarText=The archive file '{0}' expansion is in progress...
|
||||
AppendArchiveFileExtensionMessage=The archive file path '{0}' supplied to the DestinationPath patameter does not include .zip extension. Hence .zip is appended to the supplied DestinationPath path and the archive file would be created at '{1}'.
|
||||
AppendArchiveFileExtensionMessage=The archive file path '{0}' supplied to the DestinationPath parameter does not include .zip extension. Hence .zip is appended to the supplied DestinationPath path and the archive file would be created at '{1}'.
|
||||
AddItemtoArchiveFile=Adding '{0}'.
|
||||
CreateFileAtExpandedPath=Created '{0}'.
|
||||
InvalidArchiveFilePathError=The archive file path '{0}' specified as input to the {1} parameter is resolving to multiple file system paths. Provide a unique path to the {2} parameter where the archive file has to be created.
|
||||
|
|
|
|||
|
|
@ -208,8 +208,8 @@ ConvertFrom-StringData @'
|
|||
PublishLocation=Publish Location:'{0}'.
|
||||
ScriptPATHPromptCaption=PATH Environment Variable Change
|
||||
ScriptPATHPromptQuery=Your system has not been configured with a default script installation path yet, which means you can only run a script by specifying the full path to the script file. This action places the script into the folder '{0}', and adds that folder to your PATH environment variable. Do you want to add the script installation path '{0}' to the PATH environment variable?
|
||||
AddedScopePathToProcessSpecificPATHVariable=Added scripts installation location '{0}' for '{1}' scope to process specific PATH environment varaible.
|
||||
AddedScopePathToPATHVariable=Added scripts installation location '{0}' for '{1}' scope to PATH environment varaible.
|
||||
AddedScopePathToProcessSpecificPATHVariable=Added scripts installation location '{0}' for '{1}' scope to process specific PATH environment variable.
|
||||
AddedScopePathToPATHVariable=Added scripts installation location '{0}' for '{1}' scope to PATH environment variable.
|
||||
FilePathInFileListNotWithinModuleBase=Path '{0}' defined in FileList is not within module base '{1}'. Provide the correct FileList parameters and then try again.
|
||||
ManifestFileReadWritePermissionDenied=The current user does not have read-write permissions for the file:'{0}'. Check the file permissions and then try again.
|
||||
MissingTheRequiredPathOrPassThruParameter=The Path or PassThru parameter is required for creating the script file info. A new script file will be created with the script file info when the Path parameter is specified. Script file info will be returned if the PassThru parameter is specified. Try again after specifying the required parameter.
|
||||
|
|
@ -230,7 +230,7 @@ ConvertFrom-StringData @'
|
|||
SkippingPublisherCheck=Skipping the Publisher check for the version '{0}' of module '{1}'.
|
||||
SourceModuleDetailsForPublisherValidation=For publisher validation, using the previously-installed module '{0}' with version '{1}' under '{2}' with publisher name '{3}'. Is this module signed by Microsoft: '{4}'.
|
||||
NewModuleVersionDetailsForPublisherValidation=For publisher validation, current module '{0}' with version '{1}' with publisher name '{2}'. Is this module signed by Microsoft: '{3}'.
|
||||
PublishersMatch=Publisher '{0}' of the new module '{1}' with version '{2}' matches with the publisher '{3}' of the previously-installed module '{4}' with version '{5}'. Both versions are signed with a Microsoft root certifacte.
|
||||
PublishersMatch=Publisher '{0}' of the new module '{1}' with version '{2}' matches with the publisher '{3}' of the previously-installed module '{4}' with version '{5}'. Both versions are signed with a Microsoft root certificate.
|
||||
PublishersMismatch=A Microsoft-signed module named '{0}' with version '{1}' that was previously installed conflicts with the new module '{2}' from publisher '{3}' with version '{4}'. Installing the new module may result in system instability. If you still want to install or update, use -SkipPublisherCheck parameter.
|
||||
ModuleIsNotCatalogSigned=The version '{0}' of the module '{1}' being installed is not catalog signed. Ensure that the version '{0}' of the module '{1}' has the catalog file '{2}' and signed with the same publisher '{3}' as the previously-installed module '{0}' with version '{4}' under the directory '{5}'. If you still want to install or update, use -SkipPublisherCheck parameter.
|
||||
###PSLOC
|
||||
|
|
|
|||
|
|
@ -9,15 +9,15 @@ EmptyMetadata=Read metadata was empty. Url: {0}.
|
|||
InvalidEndpointAddress=Invalid endpoint address ({0}). Web response with status code '{1}' was obtained while accessing this endpoint address.
|
||||
NoEntitySets=Metadata from URI '{0}' does not contain Entity Sets. No output will be written.
|
||||
NoEntityTypes=Metadata from URI '{0}' does not contain Entity Types. No output will be written.
|
||||
MetadataUriDoesNotExist=Metadata specifed at the URI '{0}' does not exist. No output will be written.
|
||||
MetadataUriDoesNotExist=Metadata specified at the URI '{0}' does not exist. No output will be written.
|
||||
InValidIdentifierInMetadata=Metadata specified at URI '{0}' contains an invalid Identifier '{1}'. Only valid C# identifiers are supported in the generated complex types during the proxy creation.
|
||||
InValidMetadata=Failed to process metadata specified at URI '{0}'. No output will be written.
|
||||
InValidXmlInMetadata=Metadata specified at URI '{0}' contains an invalid XML. No output will be written.
|
||||
ODataVersionNotFound=Metadata specified at URI '{0}' does not contain the OData Version. No output will be written.
|
||||
ODataVersionNotSupported=The OData version '{0}' specified in the metadata located at the URI '{1}' is not supported. Only OData versions between '{2}' and '{3}' are supported by '{4}' during proxy generation. No output will be written.
|
||||
InValidSchemaNamespace=Metadata specified at URI '{0}' is invalid. NULL or Empty values are not supported for Namespace attribute in the schema.
|
||||
InValidSchemaNamespaceConflictWithClassName=Metadata specified at URI '{0}' contains invalid Namespace {1} name, which conflicts with another type name. To avoid compliation error {1} will be changed to {2}.
|
||||
InValidSchemaNamespaceContainsInvalidChars=Metadata specified at URI '{0}' contains invalid Namespace name {1} with a combination of dots and numbers in it, which is not allowed in .Net. To avoid compliation error {1} will be changed to {2}.
|
||||
InValidSchemaNamespaceConflictWithClassName=Metadata specified at URI '{0}' contains invalid Namespace {1} name, which conflicts with another type name. To avoid compilation error {1} will be changed to {2}.
|
||||
InValidSchemaNamespaceContainsInvalidChars=Metadata specified at URI '{0}' contains invalid Namespace name {1} with a combination of dots and numbers in it, which is not allowed in .Net. To avoid compilation error {1} will be changed to {2}.
|
||||
InValidUri=URI '{0}' is invalid. No output will be written.
|
||||
RedfishNotEnabled=This version of Microsoft.PowerShell.ODataUtils doesn’t support Redfish, please run: ‘update-module Microsoft.PowerShell.ODataUtils’ to get Redfish support.
|
||||
EntitySetUndefinedType=Metadata from URI '{0}' does not contain the Type for Entity Set '{1}'. No output will be written.
|
||||
|
|
@ -48,7 +48,7 @@ SkipEntitySetConflictCommandCreation=CDXML module creation has been skipped for
|
|||
EntitySetConflictCommandCreationWithWarning=CDXML module creation for the Entity Set '{0}' succeeded but contains a command '{1}' that collides with the inbox command.
|
||||
SkipConflictServiceActionCommandCreation=CDXML module creation has been skipped for the Service Action '{0}' because the exported command '{1}' conflicts with the inbox command.
|
||||
ConflictServiceActionCommandCreationWithWarning=CDXML module creation for the Service Action '{0}' succeeded but contains a command '{1}' that collides with the inbox command.
|
||||
AllowUnsecureConnectionMessage=The cmdlet '{0}' is trying to establish an Unsecure connection with the OData endpoint through the URI '{1}'. Either supply a secure URI to the -{2} parameter or use -AllowUnsecureConnection switch paramter if you intend to use the current URI.
|
||||
AllowUnsecureConnectionMessage=The cmdlet '{0}' is trying to establish an Unsecure connection with the OData endpoint through the URI '{1}'. Either supply a secure URI to the -{2} parameter or use -AllowUnsecureConnection switch parameter if you intend to use the current URI.
|
||||
ProgressBarMessage=Creating proxy for the OData endpoint at the URI '{0}'.
|
||||
###PSLOC
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Facility=POWERSHELL
|
|||
Severity=CoError
|
||||
SymbolicName=g_MANAGED_METHOD_RESOLUTION_FAILED
|
||||
Language=English
|
||||
Unable to find plugin methods WSManPluginShell, WSManPluginCommand, WSManPluginSend, WSManPluginRecieve in the Managed plugin module.
|
||||
Unable to find plugin methods WSManPluginShell, WSManPluginCommand, WSManPluginSend, WSManPluginReceive in the Managed plugin module.
|
||||
.
|
||||
|
||||
MessageId=1004
|
||||
|
|
|
|||
Loading…
Reference in a new issue