You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@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.
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.
The text was updated successfully, but these errors were encountered: