< Back
Test-UevTemplate
Post
NAME Test-UevTemplate
SYNOPSIS
Verifies whether a template complies with the schema for UE-V.
SYNTAX
Test-UevTemplate [-Path] <String[]> [<CommonParameters>]
Test-UevTemplate -LiteralPath <String[]> [<CommonParameters>]
DESCRIPTION
The Test-UevTemplate cmdlet verifies whether a settings location template complies with the XML schema for Microsoft User Experience Virtualization
(UE-V).
PARAMETERS
-LiteralPath <String[]>
Specifies an array of literal file paths. The cmdlet validates the settings location templates that have the literal paths that you specify.
Required? true
Position? named
Default value none
Accept pipeline input? True (ByPropertyName)
Accept wildcard characters? false
-Path <String[]>
Specifies an array of file paths. The cmdlet validates the settings location templates that have the paths that you specify. Use wildcards to
specify multiple files.
Required? true
Position? 1
Default value none
Accept pipeline input? True (ByValue, ByPropertyName)
Accept wildcard characters? false
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).
INPUTS
string[]
An array of paths to settings location templates.
OUTPUTS
Microsoft.UEV.Commands.TestTemplateResult
This cmdlet generates a TestTemplateResult object that contains the validation result for a settings location template.
Example 1: Test a file
PS C:\\> Test-UevTemplate -Path "MicrosoftWordpad.xml" | Format-Table -AutoSize
Path Status Message
---- ------ -------
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftWordpad.xml Valid The template is valid.
This command tests whether the specified file is a valid settings location template. The command passes the results to the Format-Table cmdlet by using
the pipeline operator. For more information, type Get-Help Format-Table.
Example 2: Test several files
PS C:\\> Test-UevTemplate -Path "*Microsoft*.xml" | Format-Table -AutoSize
Path Status Message
---- ------ -------
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftCalculator.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftInternetExplorer9.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftLync2010.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftNotepad.xml Valid The template is valid.
This command tests whether several files are valid settings location templates. The command checks all .xml files that have names that contain the
specified string. The command passes the results to Format-Table by using the pipeline operator.
Example 3: Test a file specified by its literal path
PS C:\\> Test-UevTemplate -LiteralPath "MicrosoftWordpad.xml" | Format-Table -AutoSize
Path Status Message
---- ------ -------
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftWordpad.xml Valid The template is valid.
This command tests whether the specified file is a valid settings location template file. The command passes the results to Format-Table by using the
pipeline operator.
Example 4: Test all the files in the current directory by using the pipeline
PS C:\\> Test-UevTemplate -Path "*.xml" | Format-Table -AutoSize
Path Status Message
---- ------ -------
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftCalculator.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftInternetExplorer9.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftLync2010.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftNotepad.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftOffice2010.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftVisualStudio2010.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftWindows7.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftWindows8.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftWordpad.xml Valid The template is valid.
This command uses a wildcard to test if each file is a settings location template, and then passes the results to Format-Table by using the pipeline
operator.
RELATED LINKS
Online Version: http://go.microsoft.com/fwlink/?LinkId=826058
Disable-UevTemplate
Enable-UevTemplate
Get-UevTemplate
Register-UevTemplate
Unregister-UevTemplate
Update-UevTemplate
SYNOPSIS
Verifies whether a template complies with the schema for UE-V.
SYNTAX
Test-UevTemplate [-Path] <String[]> [<CommonParameters>]
Test-UevTemplate -LiteralPath <String[]> [<CommonParameters>]
DESCRIPTION
The Test-UevTemplate cmdlet verifies whether a settings location template complies with the XML schema for Microsoft User Experience Virtualization
(UE-V).
PARAMETERS
-LiteralPath <String[]>
Specifies an array of literal file paths. The cmdlet validates the settings location templates that have the literal paths that you specify.
Required? true
Position? named
Default value none
Accept pipeline input? True (ByPropertyName)
Accept wildcard characters? false
-Path <String[]>
Specifies an array of file paths. The cmdlet validates the settings location templates that have the paths that you specify. Use wildcards to
specify multiple files.
Required? true
Position? 1
Default value none
Accept pipeline input? True (ByValue, ByPropertyName)
Accept wildcard characters? false
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).
INPUTS
string[]
An array of paths to settings location templates.
OUTPUTS
Microsoft.UEV.Commands.TestTemplateResult
This cmdlet generates a TestTemplateResult object that contains the validation result for a settings location template.
Example 1: Test a file
PS C:\\> Test-UevTemplate -Path "MicrosoftWordpad.xml" | Format-Table -AutoSize
Path Status Message
---- ------ -------
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftWordpad.xml Valid The template is valid.
This command tests whether the specified file is a valid settings location template. The command passes the results to the Format-Table cmdlet by using
the pipeline operator. For more information, type Get-Help Format-Table.
Example 2: Test several files
PS C:\\> Test-UevTemplate -Path "*Microsoft*.xml" | Format-Table -AutoSize
Path Status Message
---- ------ -------
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftCalculator.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftInternetExplorer9.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftLync2010.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftNotepad.xml Valid The template is valid.
This command tests whether several files are valid settings location templates. The command checks all .xml files that have names that contain the
specified string. The command passes the results to Format-Table by using the pipeline operator.
Example 3: Test a file specified by its literal path
PS C:\\> Test-UevTemplate -LiteralPath "MicrosoftWordpad.xml" | Format-Table -AutoSize
Path Status Message
---- ------ -------
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftWordpad.xml Valid The template is valid.
This command tests whether the specified file is a valid settings location template file. The command passes the results to Format-Table by using the
pipeline operator.
Example 4: Test all the files in the current directory by using the pipeline
PS C:\\> Test-UevTemplate -Path "*.xml" | Format-Table -AutoSize
Path Status Message
---- ------ -------
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftCalculator.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftInternetExplorer9.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftLync2010.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftNotepad.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftOffice2010.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftVisualStudio2010.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftWindows7.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftWindows8.xml Valid The template is valid.
C:\\Program Files\\Microsoft User Experience Virtualization\\Templates\\MicrosoftWordpad.xml Valid The template is valid.
This command uses a wildcard to test if each file is a settings location template, and then passes the results to Format-Table by using the pipeline
operator.
RELATED LINKS
Online Version: http://go.microsoft.com/fwlink/?LinkId=826058
Disable-UevTemplate
Enable-UevTemplate
Get-UevTemplate
Register-UevTemplate
Unregister-UevTemplate
Update-UevTemplate