Q: When does a Feature Limitation become a bug?
A: When the majority of consumers expect the functionality to be different than it actually is.
This is a BUG in the .NET Framework that has existed since its inception over 12 years ago, as it can no longer be considered a Feature Limitation. The file system and Windows API fully support long filepaths up to 32,767 characters long, as long as each folder name and filename is not more than 255 bytes long. It is time that the .NET Framework, Visual Studio, Team Foundation Server, etc., also support this.
When working on enterprise applications this becomes an extreme limitation, as it does when working on large web applications. This BUG MUST BE FIXED!
P.S. Many companies already have SANs and NAS devices that have storage capacities in the petabyte range, and many other companies are heading there as well. Even DFS (a Microsoft product) supports long file names, which is a major nightmare when your server applications start to crash. This limitation causes extreme managment and user issues when usage exceeds 260 character file paths, something that ALL of these devices support.