Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ERROR:Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware

See original GitHub issue

From @ealsur on May 20, 2016 20:11

VSCode Version:1.1.1
OS Version: Windows 10

Using C# Extension 1.0.11 and ASPNET Core RC2 (dotnet cli installed) using net461, I am unable to get Omnisharp to work.

Whenever I open a folder with a project with that version of ASPNET Core I get this error on the Omnisharp Log:

[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Processing [ProjectState] myproject/.NETFramework,Version=v4.6.1[ERROR:Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware] An unhandled exception has occurred: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

Copied from original issue: Microsoft/vscode#6592

Issue Analytics

State:
Created 7 years ago
Reactions:3
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

DustinCampbellcommented, Jul 21, 2016

This should be much better with the 1.3.0 release. In that release, we’ll be using the CoreCLR-based OmniSharp for .NET Core projects, which supports long file names. The problem is that the .NET Desktop version of OmniSharp (which we currently use on Windows) can crash with MAX_PATH issues.

1reaction

ealsurcommented, May 24, 2016

I can confirm that adding an exclude attribute to project.json fixes the issue.

The problem is that, according to the official annoucement, the exclude attribute is now deprecated on RC2 (it should be inside the buildOptions > compile tree), maybe it’s something that is still left to migrate on Omnisharp’s logic.