Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 31086 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 11595 [details]
Project which reproduces the bug.
When attempting to recursively include files in a project using MSBuild's <Link> tag, xbuild fails to correctly interpret the link. For example, if something along the lines of
is placed in a .csproj file, it will create a file called "LinkFolder\%(RecursiveDir)%(Filename)%(Extension)" in the output directory instead of copying the actual file and placing it with the appropriate file name. The same example works fine with MSBuild/Visual Studio.
I have attached an example where the behavior is demonstrated. Note that it must be built from the command line by xbuild; if it is opened in Xamarin Studio the link element's content will be (partially) urlencoded (i.e. as "%25%28RecursiveDir%29%25%28Filename%29%25%28Extension%29").
I have also verified that the behavior is still incorrect if one uses '$' instead of '%' (i.e. "LinkFolder\$(RecursiveDir)$(Filename)$(Extension)").