Say that I have the path C:\My\Multi\Component\Path . Since the shell is usually ignored on Windows, I could mix and match any shells I need to go to the same node in the file system in PowerShell:
1PS> cd C:\My\Multi\Component\Path 2PS> cd C:\my\multi\component\path 3PS> cd C:\My\multi\component\path 4PS> cd C:\my\Multi\Component\PATH
The problem is that I am using svn command line tools like svn log . . This only works if I set the location with line (1) above, i.e. using the exact shell corresponding to the base path. If I set the location with 2, 3 or 4, svn balks, for example:
svn: svn: E155010: The node 'C:\My\multi\component\path' was not found.
I understand that the fact that svn is case sensitive while Windows is not the cause of this problem and I can live with it. But I want a workaround, namely: a way to find the base one, furnished as the source path in PowerShell. Then I can send my way through this normalization filter before passing it to svn. Unfortunately, PowerShell refuses to provide a true, basic path to me. I learned all the properties of Get-Location, Get-Item and Get-ChildItem.
Is there a way to get the true path?
source share