>>In that case, the 3 blog entries at http://blogs.msdn.com/b/bclteam/archive/2007/02/13/long-paths-in-net-part-1-of-3-kim-hamilton.aspx are probably worth a look.
>
>It is certainly quite a challenge for Microsoft to make it easier for us when we have to go over 260 characters. It seems to what I mentioned in my last message. Some of workarounds may apply but at one time or another, it will just not work depending on what kind of manipulation we have to do with the file. BTW, is there any update on that in Windows 8. Can someone confirm if this is still the same limit?

While skimming those blogs, I got the impression that if you want complete, seamless support for long file names/paths, it ain't gonna happen, up to and including Win7/Server 2008. Win8/Server 2012, I don't know. I haven't heard anything about that limit being lifted; if it were, my guess is a *lot* of 3rd-party software would break upon hitting a file/path over 260 chars.

The blog entries do show some workarounds for common use cases. If you want to do something else, you're on your own e.g. zipping, you'd need to test any utility to use to check for long file/path support.