Add longPathAware manifest to NuGet.Build.Tasks.Console #4830
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug
Fixes: NuGet/Home#12121
Regression? No
Description
Copied https://github.com/dotnet/roslyn/blob/ee9808b0ec1d5b94dba1ade21319b61487588ced/src/Compilers/Core/Portable/Resources/default.win32manifest
then added
windowsSettings
andlongPathAware
as per blog post: https://learn.microsoft.com/en-us/archive/blogs/jeremykuhne/net-4-6-2-and-long-paths-on-windows-10PR Checklist
PR has a meaningful title
PR has a linked issue.
Described changes
Tests
longPathAware
element, but it turned out to be too difficult. Similarly, to write a test to validate the app can read/write long paths would require starting it as a new process, which means generating valid input files, which again is in my opinion not worth the effort.Documentation