Could not write lines to file "obj\Debug\net5.0\SolutionName.GeneratedMSBuildEditorConfig.editorconfig exceeds the OS max path limit

Question

I was doing a project, I runned 1 time and it was fine, I runned the second time and this error appeard "Could not write lines to file "obj\Debug\net5.0\SolutionName.GeneratedMSBuildEditorConfig.editorconfig exceeds the OS max path limit. The fully qualified file name must be less than 260 characteres. SolutionName C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\Roslyn\Microsoft.Managed.Core.targets 150".

So I did a little research and the most common response was to re-install visual studio, so i did, but the error continued. So i create a new program and without doing any changes, in the new program, the same erros ocurred. The only thing i have in this new program is the main class with an "Hello world".

I assume its not a code problem and i can't find anything that answers why this error is appearing.

Try to move your project/solution to a folder with shorter path — Klaus Gütter, Mar 09 '21 at 17:08
What is the path of the project you're trying to compile? Is it a really long directory name? — Martin Costello, Mar 09 '21 at 17:08
@KlausGütter It worked, but why did the project only show this error after the first successful run? — Rubs Bieira, Mar 09 '21 at 17:11
@MartinCostello It is but the first time I runned it, it wasnt an issue. — Rubs Bieira, Mar 09 '21 at 17:13
But what is the path? You haven't actually given it, so we can't determine if it's more than 260 characters, which is the MAX_PATH limit on Windows. — Martin Costello, Mar 09 '21 at 17:33
@MartinCostello the path has more than 260, that part I understod. The parte that i dont understand is why I could run the program successful once before the error — Rubs Bieira, Mar 09 '21 at 17:41
My guess would be something a _rebuild_ does is hitting the MAX_PATH limit. If that's the case, the only fix is likely to be moving your project to a location on disk with a shorter path. — Martin Costello, Mar 09 '21 at 17:44
Map your long path to a drive letter, like X:, and use that. — Dour High Arch, Mar 09 '21 at 18:42

Hamed Lohi · Answer 1 · 2021-12-04T08:06:24.153

11

I have same error, and that is related with 'file name must be less than 260 characters' and resolved by Enabling Windows Long Path via reference link: https://www.microfocus.com/documentation/filr/filr-4/filr-desktop/t47bx2ogpfz7.html

or do the following steps:

1- Click Window key and type gpedit.msc, then press the Enter key. This launches the Local Group Policy Editor.

2- Navigate to Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem.

3- Double click Enable NTFS long paths.

4- Select Enabled, then click OK.

5- at last restart visual studio

edited Dec 04 '21 at 08:06

answered Nov 30 '21 at 08:51

Hamed Lohi

432
4
10

2

This worked for me. Thank you. – Greg Graham Feb 16 '22 at 20:47
1

Caveat that this required a reboot for me. – Marc L. Mar 11 '22 at 21:05

score 9 · Accepted Answer · edited Apr 12 '21 at 11:35

9

I have also experienced a similar issue. I resolved it by moving my project to the root of my C: Drive to try and shorten the name and the path of the project.

edited Apr 12 '21 at 11:35

Dharman

26,923
21
73
125

answered Apr 12 '21 at 11:29

Quince Ngomane

172
1
15

i already fixed and that was it, the path to the project was to long, the only thing is that i dont know how could i run the program for like a week without any problems and in one day it wouldn work anymore. – Rubs Bieira Apr 15 '21 at 15:30

Could not write lines to file "obj\Debug\net5.0\SolutionName.GeneratedMSBuildEditorConfig.editorconfig exceeds the OS max path limit

2 Answers2

Linked