Tip: You can use a temporary file (ex: script, function, …) and then just clean up (delete) at the end once you don’t need that.
Instead of hardcoding a path for a temporary file, you can use the GetTempFileName method.
In PowerShell v5, there is a new cmdlet : New-TemporaryFile
|
1 2 3 4 5 6 7 8 9 10 |
# Create # PowerShell v4 (and earlier) $tempFile = [System.IO.Path]::GetTempFileName() # PowerShell v5 $tempFile = New-TemporaryFile # Delete Remove-Item -Path $tempFile |
Pingback: Powershell Tip #37: Determine the Forest and Domain functional levels | Powershell Guru
The method name is a little deceptive. It not only generates a name, it creates the associated (empty) file. So it is incumbent upon you, the scripter, to clean up after yourself.
True, I agree with you. I often use this method to avoid hardcoding paths but the inconvenient is that the scripter needs to clean up the created file.
Pingback: Powershell Tip #35: List and remove a function | Powershell Guru