-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support long paths in compilers & compiler servers #32804
Comments
A few gotchas:
<?xml version="1.0" encoding="utf-8"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity version="$(AssemblyVersion)" name="$(AssemblyName)" />
<application xmlns="urn:schemas-microsoft-com:asm.v3">
<windowsSettings xmlns:ws2="http://schemas.microsoft.com/SMI/2016/WindowsSettings">
<ws2:longPathAware>true</ws2:longPathAware>
</windowsSettings>
</application>
</assembly>
|
I am not sure why this issue is closed. Value |
It's closed because it was thought to be fixed. :) @astrohart What issues area you having? |
Since there was no answer from astrohart, I'll jump in to mention I'm also still having issues with paths being too long in vs 2019.
Am I missing some other fix related to vs 2019 alone? |
@danutzplusplus Visual Studio support for long paths is tracked by this VS feedback item https://developercommunity.visualstudio.com/t/allow-building-running-and-debugging-a-net-applica/351628. |
Thanks a bunch for linking the item. |
Ideally, the compilers (in their various forms) would support using files with paths that exceed
MAX_PATH
.This requires several changes to coordinate to convince Windows and .NET to support long paths:
longPathAware
app.config
)Long paths were enabled for MSBuild 16.0 in dotnet/msbuild#3507; similar changes would need to be made for each of the Roslyn executables.
Simple repro of
csc.exe
failing here:Version Used:
231aeb8
Steps to Reproduce:
Alternately, in MSBuild, using the compiler server:
The text was updated successfully, but these errors were encountered: