On line six, we see the first item in the converted JSON array. $json = Get-Content $file.FullName | ConvertTo-JsonĬopy-Item $file.FullName -Destination $targetDir $files = Get-ChildItem $sourceDir -filter 2020*.json For example: [Įxpand the script from the previous section to add a check for that date as well: $sourceDir = 'C:\tmp\logs' In our example, the JSON log files contain an array wherein the first item is the date the file was generated. This, however, only offers basic text editing functionality.įor more advanced features, it's best to switch over to Visual Studio Code for PowerShell debugging. Type in a command and then press Shift-Enter to start a new line. It's also possible to write a multiline script interactively in PowerShell. PowerShell does enable admins to write long one-liners, but they can easily become too unwieldy to debug. It's possible to make this snippet a little more intelligent - for example, check the contents of the file to ensure the timestamp inside the log file is also this year. Then, enter this one-liner (note: since we're running this command interactively, it is acceptable to use aliases, which are command shortcuts or alternate names): gci $sourceDir -filter *20*.json | % Let's say we're writing a snippet of code to search the current directory for JSON log files that have the year 2020 in the name and then copy those files to another directory.īefore running a script at the console, set some required variables interactively at the prompt: $sourceDir = 'C:\tmp\logs' Visual Studio Code for PowerShell debugging.
This tutorial walks through examples that further demonstrate when to use the console vs. For short scripts, the console offers plenty of debugging features, but to debug longer scripts or even modules, use an editor such as Visual Studio Code. There are two common options to debug a PowerShell script: the interactive PowerShell console, or one of many PowerShell code editors.
0 kommentar(er)
