Hi,
A powershell noob here...

I have a Powershell script that is calling Invoke-Sqlcmd and passing in a file to be executed using its -InputFile property. i.e.:
Invoke-Sqlcmd -ServerInstance . -database MyDB -InputFile ".\Script.sql"

Script.sql is stored in the same place as my Powershell script.

When I run the Powershell script I get an error:
Invoke-Sqlcmd : Could not find file 'C:\Windows\System323\Script.sql'

Clearly the relative path ".\Script.sql" is not behaving like I thought it would.

How do I reference a path stored in the same folder using a relative path? Surely this can be done, can't it?

Is there a solution to this? Something that works in POSH v1 would be preferable.

thanks
Jamie

Ah, looks like
Get-Location
does what I need!

Get-Location is [System.Environment]::CurrentDirectory, which is what you don't want. You want this:

$scriptDirectory = Split-Path -Path $script:MyInvocation.MyCommand.Path -Parent

You can use the resolve-path cmdlet:

-InputFile (resolve-path .\Script.sql).Path

nice, thank you guys.

And out of interest, what's the problem with [System.Environment]::CurrentDirectory? Its doing what I expect it to.

Its fine as long as you use Set-Location to set the correct path, otherwise its gets the location of the current working directory, which could be anything.

PowerShell has a current location for each PSDrive it knows about. Some of these are not even filesystems. [System.Environment]::CurrentDirectory gets the current directory for the powershell.exe process rather than the current PSDrive's location.

Using Get-Location only fixes part of the problem because it depends on the currently selected PSDrive. What is the path to your script if by some reason you are called from HKLM:\Software\Microsoft? Using Get-Location or Resolve-Path will likely result in something similar to HKLM:\Software\Microsoft\Script.sql which is clearly wrong. If your powershell script and script.sql exist in C:\Temp\Scripts but they user is currently in C:\Users\username, then using Get-Location will still not find the script because it results in C:\Users\username\script.sql.