Skip to content
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

dx: better guide potential contributors on dealing with 'path-too-long'-errors on windows #11139

Open
earloc opened this issue Nov 2, 2024 · 0 comments · May be fixed by #11140
Open

dx: better guide potential contributors on dealing with 'path-too-long'-errors on windows #11139

earloc opened this issue Nov 2, 2024 · 0 comments · May be fixed by #11140
Milestone

Comments

@earloc
Copy link
Contributor

earloc commented Nov 2, 2024

@davidwengier , @ryzngard this is a followup issue on our recent discussion, which popped up during work on #11124

steps to reproduce:

  • Checkout a fresh copy of this repo on a windows machine w/o enabled support for long-paths
  • run the ./build.cmd
  • observe errors occuring, such as:
error MSB4248: Cannot expand metadata in expression "$([MSBuild]::ValueOrDefault('%(FullPath)','').StartsWith($([MSBuild]::EnsureTrailingSlash($(MSBuildProjectDirectory)))))".
The item metadata "%(FullPath)" cannot be applied to the path "TestFiles\IntegrationTests\ComponentDesignTimeCodeGenerationTest\GenericComponent_GenericEventCallbackWithGenericTypeParameter_NestedTypeInference\TestComponent.mappings.txt". 
Path: {{PATH-TO-REPOSITORY}}\src\Compiler\Microsoft.AspNetCore.Razor.Language\test\TestFiles\IntegrationTests\ComponentDesignTimeCodeGenerationTest\GenericComponent_GenericEventCallbackWithGenericTypeParameter_NestedTypeInference\TestComponent.mappings.txt exceeds the OS max path limit.
The fully qualified file name must be less than 260 characters. [{{PATH-TO-REPOSITORY}}\src\Compiler\Microsoft.AspNetCore.Razor.Language\test\Microsoft.AspNetCore.Razor.Language.Test.csproj]

expected
Something telling me that I need to enable long path support, or other directions that I should be aware of when starting to contribute to this repo.

actual
Only errors occuring.

@earloc earloc linked a pull request Nov 2, 2024 that will close this issue
@chsienki chsienki removed the untriaged label Nov 7, 2024
@chsienki chsienki added this to the 17.13 P2 milestone Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants