..that applies sometimes, depending on the application, but not all the time, depending on the application..
WTF and how the heck do you all deal with this? I have users who are able to create insanely long filenames and paths, yet who aren't then able to open those files and folders in certain applications, with seemingly no way at all for me to stop them from doing it.
I can't be the only one finding it an issue..
Path length limitations are a bummer. Fortunately you're not the only one who has thought about it. There's a series of blog postings about long paths in .NET that can give you some background on the status of long path support in .NET. There's a least one library that adds long path support that you can use (license permitting, of course).