Despite the fact that its 2016, Visual Studio still can't seem to handle filepaths greater than 255 characters...

@g-m-f No not at all. In fact I can work around it by creating the project under an abbreviated filepath, closing VS, moving the project file to the desired full filepath, and then hand edit the solution file to look for the project in the new path.

My only guess is that it causes issues with TFVC, but i use git plus it never seemed to hurt TFS either...