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

"@" in path broke "copy always" option for files in .net9 sdk #46987

Open
HerrTete opened this issue Feb 20, 2025 · 4 comments
Open

"@" in path broke "copy always" option for files in .net9 sdk #46987

HerrTete opened this issue Feb 20, 2025 · 4 comments
Assignees
Labels
needs team triage Requires a full team discussion untriaged Request triage from a team member

Comments

@HerrTete
Copy link

Describe the bug

Since .net9 files with "Always" are no longer copied to the outputfolder if the path of the projectfolder or any folder above it contains a "@". We found this behavior on our jenkins, because he creates for each worker a folder containing a "@".

To Reproduce

  1. Create a folder like "test@dotnet"
  2. Create a new dotnet console application
  3. add a file with "copy always"
  4. build
  5. => the file isnt copied

workarounds
option 1
create a global.json force to dotnet 8 sdk and retry
option 2
remove the "@" from the foldername

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Request triage from a team member label Feb 20, 2025
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

1 similar comment
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@allenh9999
Copy link

I also have an issue where the files that are set to copy always and don't copy over have a set of parenthesis, like (1).
Perhaps these 2 issues are related?

@edvilme
Copy link
Member

edvilme commented Mar 11, 2025

Looks similar to #46833 (i.e., related to characters being escaped incorrectly and not being able to find the location), although I think this is an MSBuild issue?

@edvilme edvilme added the needs team triage Requires a full team discussion label Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs team triage Requires a full team discussion untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

3 participants