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 15704 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
In xbuild, using a Wildcard character in an Import element results in a runtime error. For example, the following statement results in an error saying that the file cannot be found:
However, the above statement works correctly in MS Build - the list of matching projects is resolved correctly and all of the matching files are successfully imported.
This error appears to be inconsistent. In our application we had two identical use-cases of such a wildcard character in an Import. One resulted in an error and the other did not. From what we can tell there were no logical differences between the use-cases that should be causing the error. In both cases it was supported by MS Build without any issues.