This type of path is composed of components separated by backslashes, each up to the value returned in the lpMaximumComponentLength parameter of the GetVolumeInformation function (this value is commonly 255 characters).

The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters. I wondered, how big can those architectural changes be (for MSBuild)?Īccording to Naming Files, Paths, and Namespaces: Maximum Path Length Limitation, (which I have mirrored here ):

Dedicating resources to this work item would come at the expense of many other features and innovation. We understand that this can be a frustrating issue, however, fixing it requires a large and complicated architectural change across different products and features including Visual Studio, TFS, MSBuild and the. Will Buik's response w/regard to fixing it was:

As seen in Fix 260 character file name length limitation, there's quite a bit of support for better longer-than- MAX_PATH-filename handling.