A lot of people use Select-String but I haven\u2019t seen much discussion of the \u2013Context parameter. This is an awesome feature that we added in V2. If you haven\u2019t tried it, you should spend a few minutes experimenting. I can guarantee you that will you be glad you did.<\/p>\n
Let\u2019s see what the HELP has to say about the Context parameter:<\/p>\n
<\/p>\n
PS> Get-Help Select-String -Parameter Context <\/font><\/p>\n -Context <Int32[]> If you enter one number as the value of this parameter, that number determi In the default display, lines with a match are indicated by a right angle b This parameter does not change the number of objects generated by Select-St When you pipe the output of a Select-String command to another Select-Strin When the context includes a match, the MatchInfo object for each match incl Required? false <\/p>\n Let\u2019s have some fun. I\u2019m going to use Superstar James O\u2019Neil\u2019s Hypervisor Management Library<\/a> to experiment with. He has a number of functions the work with NICs. Let\u2019s party.<\/p>\n PS> #First Let’s find the functions network.ps1:3:Function Add-VMNIC <\/font><\/p>\n <\/font><\/p>\n PS> # That gave me too many so let’s add a $ to the end of the SEARCH STRING<\/strong> network.ps1:3:Function Add-VMNIC <\/font><\/p>\n <\/font><\/p>\n PS> # Let’s see 1 line before and after each matching line network.ps1:2<\/font>: PS> # Notice the line numbers and that the matching line has a > in front<\/strong><\/font><\/p>\n <\/strong><\/font><\/p>\n <\/strong> <\/p>\n <\/p>\n <\/font>PS> # Now let’s try 3 lines before and after the matching line network.ps1:1: <\/font><\/p>\n <\/font><\/p>\n PS> # The line before is boring so let’s get rid of that and then see a > network.ps1:3:Function Add-VMNIC <\/p>\n <\/p>\n PS> # Let’s take a look at the body of Remove-VMNIC > network.ps1:282:Function Remove-VMNIC <\/p>\n Party on your own. You are going to love \u2013Context!<\/p>\n Experiment! Enjoy! Engage! <\/p>\n Jeffrey Snover [MSFT] A lot of people use Select-String but I haven\u2019t seen much discussion of the \u2013Context parameter. This is an awesome feature that we added in V2. If you haven\u2019t tried it, you should spend a few minutes experimenting. I can guarantee you that will you be glad you did. Let\u2019s see what the HELP has […]<\/p>\n","protected":false},"author":600,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2991","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell"],"acf":[],"blog_post_summary":" A lot of people use Select-String but I haven\u2019t seen much discussion of the \u2013Context parameter. This is an awesome feature that we added in V2. If you haven\u2019t tried it, you should spend a few minutes experimenting. I can guarantee you that will you be glad you did. Let\u2019s see what the HELP has […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/2991","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/600"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=2991"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/2991\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=2991"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=2991"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=2991"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Captures the specified number of lines before and after the line with the m
atch. This allows you to view the match in context. <\/font><\/p>\n
nes the number of lines captured before and after the match. If you enter t
wo numbers as the value, the first number determines the number of lines be
fore the match and the second number determines the number of lines after t
he match. <\/font><\/p>\n
racket (ASCII 62) in the first column of the display. Unmarked lines are th
e context. <\/font><\/p>\n
ring. Select-String generates one MatchInfo (Microsoft.PowerShell.Commands.
MatchInfo) object for each match. The context is stored as an array of stri
ngs in the Context property of the object. <\/font><\/p>\n
g command, the receiving command searches only the text in the matched line
(the value of the Line property of the MatchInfo object), not the text in
the context lines. As a result, the Context parameter is not valid on the r
eceiving Select-String command. <\/font><\/p>\n
udes all of the context lines, but the overlapping lines appear only once i
n the display. <\/font><\/p>\n
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false<\/font><\/p>\n
PS> dir *.ps1 |Select-String function.*NIC<\/strong> <\/font><\/p>\n
network.ps1:64:Function Get-VMNic
network.ps1:94:Function Get-VMNicport
network.ps1:104:Function Get-VMnicSwitch
network.ps1:121:Function Get-VMNICVLAN
network.ps1:282:Function Remove-VMNIC
network.ps1:332:Function remove-VMSwitchNIC
network.ps1:366:Function Select-VMNIC
network.ps1:392:Function Set-VMNICAddress
network.ps1:422:Function Set-VMNICSwitch
network.ps1:459:Function Set-VMNICVLAN <\/font><\/p>\n
PS> # That indicates a Line end
<\/strong>PS> dir *.ps1 |Select-String function.*NIC$ <\/font><\/strong><\/font><\/p>\n
network.ps1:64:Function Get-VMNic
network.ps1:282:Function Remove-VMNIC
network.ps1:366:Function Select-VMNIC<\/font><\/p>\n
<\/strong>PS> dir *.ps1 |Select-String function.*NIC$ -Context 1 <\/strong><\/font><\/p>\n
><\/font> network.ps1:3<\/font>:Function Add-VMNIC
network.ps1:4<\/font>:{# .ExternalHelp MAML-VMNetwork.XML
network.ps1:63:
> network.ps1:64:Function Get-VMNic
network.ps1:65:{# .ExternalHelp MAML-VMNetwork.XML
network.ps1:281:
> network.ps1:282:Function Remove-VMNIC
network.ps1:283:{# .ExternalHelp MAML-VMNetwork.XML
network.ps1:365:
> network.ps1:366:Function Select-VMNIC
network.ps1:367:{# .ExternalHelp MAML-VMNetwork.XML <\/font><\/p>\n
<\/strong>PS> dir *.ps1 |Select-String function.*NIC$ -Context 3 <\/strong><\/font><\/p>\n
network.ps1:2:
> network.ps1:3:Function Add-VMNIC
network.ps1:4:{# .ExternalHelp MAML-VMNetwork.XML
network.ps1:5: [CmdletBinding(SupportsShouldProcess=$true)]
network.ps1:6: param(
network.ps1:61:}
network.ps1:62:
network.ps1:63:
> network.ps1:64:Function Get-VMNic
network.ps1:65:{# .ExternalHelp MAML-VMNetwork.XML
network.ps1:66: param(
network.ps1:67: [parameter(ValueFromPipeline = $true)]
network.ps1:279:}
network.ps1:280:
network.ps1:281:
> network.ps1:282:Function Remove-VMNIC
network.ps1:283:{# .ExternalHelp MAML-VMNetwork.XML
network.ps1:284: [CmdletBinding(SupportsShouldProcess=$true)]
network.ps1:285: param(
network.ps1:363:
network.ps1:364:
network.ps1:365:
> network.ps1:366:Function Select-VMNIC
network.ps1:367:{# .ExternalHelp MAML-VMNetwork.XML
network.ps1:368: param(
network.ps1:369: [parameter(ValueFromPipeline = $true)]<\/font><\/p>\n
<\/strong>PS> # few lines after
<\/strong>PS> dir *.ps1 |Select-String function.*NIC$ -Context 0,3<\/strong> <\/font><\/p>\n
network.ps1:4:{# .ExternalHelp MAML-VMNetwork.XML
network.ps1:5: [CmdletBinding(SupportsShouldProcess=$true)]
network.ps1:6: param(
> network.ps1:64:Function Get-VMNic
network.ps1:65:{# .ExternalHelp MAML-VMNetwork.XML
network.ps1:66: param(
network.ps1:67: [parameter(ValueFromPipeline = $true)]
> network.ps1:282:Function Remove-VMNIC
network.ps1:283:{# .ExternalHelp MAML-VMNetwork.XML
network.ps1:284: [CmdletBinding(SupportsShouldProcess=$true)]
network.ps1:285: param(
> network.ps1:366:Function Select-VMNIC
network.ps1:367:{# .ExternalHelp MAML-VMNetwork.XML
network.ps1:368: param(
network.ps1:369: [parameter(ValueFromPipeline = $true)]<\/font><\/p>\n
<\/strong>PS> dir *.ps1 |Select-String function.*Remove-VMNIC$ -Context 0,20 <\/strong><\/font><\/p>\n
network.ps1:283:{# .ExternalHelp MAML-VMNetwork.XML
network.ps1:284: [CmdletBinding(SupportsShouldProcess=$true)]
network.ps1:285: param(
network.ps1:286: [parameter(Mandatory = $true , ValueFromPipeline = $true)]
network.ps1:287: $Nic,
network.ps1:288:
network.ps1:289: $PSC,
network.ps1:290: [switch]$force,
network.ps1:291:
network.ps1:292: $VM, $Server #VM no longer required, but preserved for compatibility with V1
network.ps1:293: )
network.ps1:294: process {
network.ps1:295: if ($psc -eq $null) {$psc = $pscmdlet} ; if (-not $PSBoundParameters.psc) {$PSBoundParameter
s.add("psc",$psc)}
network.ps1:296: if ($NIC -is [Array] ) {[Void]$PSBoundParameters.Remove("NIC") ; $NIC | ForEach-object {Remo
ve-VMNIC -NIC $_ @PSBoundParameters}}
network.ps1:297: if ($nic -is [System.Management.ManagementObject]) {remove-VMRasd -rasd $NIC -PSC $psc }
network.ps1:298: # note: In V1 the switch port was removed before removing the NIC, but this is done autom
atically.
network.ps1:299: }
network.ps1:300:}
network.ps1:301:
network.ps1:302:<\/font><\/p>\n
Distinguished Engineer
Visit the Windows PowerShell Team blog at: http:\/\/blogs.msdn.com\/PowerShell<\/a>
Visit the Windows PowerShell ScriptCenter at: http:\/\/www.microsoft.com\/technet\/scriptcenter\/hubs\/msh.mspx<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"