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

DestinationSubDirectory does not work recursively #11400

Open
CEbbinghaus opened this issue Feb 7, 2025 · 1 comment
Open

DestinationSubDirectory does not work recursively #11400

CEbbinghaus opened this issue Feb 7, 2025 · 1 comment
Assignees
Labels

Comments

@CEbbinghaus
Copy link

This is a bit of an unexpected behavior for me, although I doubt it counts as a bug given that it probably wasn't intended.

the <DestinationSubDirectory> attribute works fine when we are talking about implicit references. But I would have expected it to work recursively up the directory structure. To this end I have created a reproduction repository:
https://github.com/CEbbinghaus/DestinationSubDirectoryRepro

It's probably not trivial to implement but having functionality like this would go a long way to keeping the root directory clear and being able to better organize libraries.

@rainersigwald
Copy link
Member

@CEbbinghaus what led you to think that specifying DestinationSubDirectory metadata in this way would have an effect? The only docs I see for it are as an output of a task.

The .NET SDK doesn't (today) provide much help with collections of related executables--you may wish to follow the related issue dotnet/sdk#18282.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants