by LarryWeiss at 2012-10-09 12:50:42
Don Jones opened this issue back in 2007 and I have a feeling it is still not resolved in PowerShell V3.by DonJ at 2012-10-09 12:55:38
https://connect.microsoft.com/PowerShel … ns#details
Is there anything new to report on PowerShell’s tolerance for long paths ?
As noted in that Connect ticket comment from Microsoft, PowerShell’s fine with long paths. .NET Framework isn’t - which PowerShell is built on - and to my knowledge, no, that hasn’t been addressed.by LarryWeiss at 2012-10-09 13:03:45
I suppose then that there is an open ticket somewhere in .Net Framework support at Microsoft.by DonJ at 2012-10-09 13:08:51
Does anyone have a link to it if it exists?
It’s internally a “known issue.” It’s been that way for longer than the .NET team has been involved with Connect, so no, as far as I know there’s no public ticket I can point you to.by LarryWeiss at 2012-10-09 13:48:21
Some web searches later…
http://blogs.msdn.com/b/bclteam/archive … ilton.aspx
describes the state of affairs in 2007 in a general .NET context.
http://www.pinvoke.net/default.aspx/Con … _PATH.html
is a concise statement of the limits, with language constants you can use to code it into your logic.
That article also has mention of workarounds.
Seem’s that .NET is “blaming” it on the Windows API. Such a house of cards!