"Could not find a part of the path" using VS 2022 msbiuld

[aburgett87]

When opening a solution with a long file path in VS Code using either VS 2022 msbuild or the standalone msbiuld the intellisense is broken.

The console app project will execute correctly when running dotnet run and VS 2022 correctly displays the solution.

I receive an error "Could not find a part of the path" in the omnisharp logs.

C# extension version v1.23.16

MS Build versions:

1. Visual Studio Professional 2022 17.0.31825.309 17.0.0
2. StandAlone 17.0.0

O/S: Windows 10 (21H1) Build 19043.1288

Log File: scratch2.txt

Reproducible solution: test-proj.zip

Logs of interest:

[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: c:\Users\AlexBurgett\devel\temp\test-proj\src\A.Really.Long.Long.Long.Long.Long.File.Path.That.Is.Really.Long.I.Mean.Really.Long\A.Really.Long.Long.Long.Long.Long.File.Path.That.Is.Really.Long.I.Mean.Really.Long.csproj
[fail]: OmniSharp.MSBuild.ProjectLoader
        Could not find a part of the path 'c:\Users\AlexBurgett\devel\temp\test-proj\src\A.Really.Long.Long.Long.Long.Long.File.Path.That.Is.Really.Long.I.Mean.Really.Long\obj\Debug\net6.0\A.Really.Long.Long.Long.Long.Long.File.Path.That.Is.Really.Long.I.Mean.Really.Long.GeneratedMSBuildEditorConfig.editorconfig'.
[warn]: OmniSharp.MSBuild.ProjectManager
        Failed to load project file 'c:\Users\AlexBurgett\devel\temp\test-proj\sr
c\A.Really.Long.Long.Long.Long.Long.File.Path.That.Is.Really.Long.I.Mean.Really.Long\A.Really.Long.Long.Long.Long.Long.File.Path.That.Is.Really.Long.I.Mean.Really.Long.csproj'.
c:\Users\AlexBurgett\devel\temp\test-proj\src\A.Really.Long.Long.Long.Long.Long.File.Path.That.Is.Really.Long.I.Mean.Really.Long\A.Really.Long.Long.Long.Long.Long.File.Path.That.Is.Really.Long.I.Mean.Really.Long.csproj
C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin\Roslyn\Microsoft.Managed.Core.targets(190,5): Error: Could not find a part of the path 'c:\Users\AlexBurgett\devel\temp\test-proj\src\A.Really.Long.Long.Long.Long.Long.File.Path.That.Is.Really.Long.I.Mean.Really.Long\obj\Debug\net6.0\A.Really.Long.Long.Long.Long.Long.File.Path.That.Is.Really.Long.I.Mean.Really.Long.GeneratedMSBuildEditorConfig.editorconfig'.

[schuettecarsten]

I have the same issue, but I was able to fix it by enabling "long path support" in Windows 10: https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation

[aburgett87]

@schuettecarsten I've got long paths enabled in the registry.

Interestingly, following the page you provided, the application's manifest must be long path aware. I checked the msbuild exe's manifest and it is long path aware, but the omnisharp.exe isn't.

[aburgett87]

The manifest file was the issue, by adding an app.manifest and enabling long paths (see https://github.com/OmniSharp/omnisharp-roslyn/pull/2298) I was able to successfully utilise omnisharp in vscode

[KamranShahid]

But why in VS2022 only. same thing build in VS 2019

[mbritov]

I have the same issue, but I was able to fix it by enabling "long path support" in Windows 10: https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation

Thanks, it helped me too

[ivanko337]

I have the same issue, but I was able to fix it by enabling "long path support" in Windows 10: https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation

I had an issue that .NET can't build the .editorconfig with a long path file and this is helped

[javedali-dev]

I have the same issue, but I was able to fix it by enabling "long path support" in Windows 10: https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation

I had the same issue in the VS2022 with Windows 11. and this helped.

[jarnedhaene]

I have the same issue, but I was able to fix it by enabling "long path support" in Windows 10: https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation

Sorry to bump, but fixed my issue aswell.

[Proud-Sachinda]

Thank you guys, https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry, also fixed my issue.

[marcosrobles-qo]

it works!