New-PefKeyDownTrigger

Windows Server 2012 R2 and Windows 8.1

New-PefKeyDownTrigger

Creates a trigger that signals when a user presses a key.

Sintaxis

Parameter Set: Default
New-PefKeyDownTrigger [-InformationAction <System.Management.Automation.ActionPreference> {SilentlyContinue | Stop | Continue | Inquire | Ignore | Suspend} ] [-InformationVariable <System.String> ] [-Key <Char[]> ] [-Repeat] [ <CommonParameters>]




Descripción detallada

The New-PefKeyDownTrigger cmdlet creates a trigger that signals when a user presses a specified key. Use the Key parameter to specify the key to initiate a trigger. You can use this keystroke trigger to start or stop a Protocol Engineering Framework (PEF) Trace Session. The trigger becomes active when you associate it with a PEF action.

Parámetros

-InformationAction<System.Management.Automation.ActionPreference>

Specifies how this cmdlet responds to an information event. Los valores aceptables para este parámetro son los siguientes:

-- SilentlyContinue
-- Stop
-- Continue
-- Inquire
-- Ignore
-- Suspend


Alias

infa

¿Requerido?

false

¿Posición?

named

Valor predeterminado

none

¿Aceptar canalización?

false

¿Aceptar caracteres comodín?

false

-InformationVariable<System.String>

Specifies a variable in which to store an information event message.


Alias

iv

¿Requerido?

false

¿Posición?

named

Valor predeterminado

none

¿Aceptar canalización?

false

¿Aceptar caracteres comodín?

false

-Key<Char[]>

Specifies a key to initiate a trigger. Note that Ctrl+C is no longer supported.


Alias

none

¿Requerido?

false

¿Posición?

named

Valor predeterminado

none

¿Aceptar canalización?

false

¿Aceptar caracteres comodín?

false

-Repeat

Indicates that the trigger runs on each occurrence of the keyboard input that you specify. If you do not specify this parameter, the trigger runs only once.


Alias

none

¿Requerido?

false

¿Posición?

named

Valor predeterminado

none

¿Aceptar canalización?

false

¿Aceptar caracteres comodín?

false

<CommonParameters>

Este cmdlet admite los siguientes parámetros comunes: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer y -OutVariable. Para obtener más información, consulte about_CommonParameters (http://go.microsoft.com/fwlink/p/?LinkID=113216).

Entradas

El tipo de entrada es el tipo de los objetos que se pueden canalizar al cmdlet.

Salidas

El tipo de resultado es el tipo de objetos que emite el cmdlet.

Ejemplos

Example 1: Save the contents of a Trace Session with a key down trigger

This example creates a PEF Trace Session that you can save at any time by using the keyboard S key as a shortcut.

The first command uses the New-PefTraceSession cmdlet to create a Trace Session that runs in the Circular mode, and stores a Trace Session object in the $TraceSession01 variable.

The second command uses the Add-PefMessageSource cmdlet to add the specified message trace source.

The third command uses the current cmdlet to create a trigger based on the keyboard shortcut S and stores it in the $Trigger01 variable.

The fourth command creates a save action for the Trace Session stored in the $TraceSession01 variable, which uses the trigger specified in the $Trigger01 variable. The command also specifies a name for the trace file to save. In addition, the command uses the Force parameter and therefore does not prompt you before replacing an existing file.

The final command uses the Start-PefTraceSession cmdlet to start the session.


PS C:\> $TraceSession01 = New-PefTraceSession -Mode Circular -SaveOnStop
PS C:\> Add-PefMessageSource -PEFSession $TraceSession01 –Source "Microsoft-Pef-WFP-MessageProvider"
PS C:\> $Trigger01 = New-PefKeyDownTrigger -Key S
PS C:\> Save-PefDataCollection -PEFSession $TraceSession01 -Path "C:\Traces\Trace01.matu" -Force -Trigger $Trigger01
PS C:\> Start-PefTraceSession -PEFSession $TraceSession01

Temas relacionados

Adiciones de comunidad

AGREGAR
Mostrar: