Bug 15704 - xbuild: Wildcard characters are not supported in an Import
Summary: xbuild: Wildcard characters are not supported in an Import
Status: NEW
Alias: None
Product: Tools
Classification: Mono
Component: xbuild ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-10-25 11:41 UTC by Brandon Lyn
Modified: 2013-10-25 11:43 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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 original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Brandon Lyn 2013-10-25 11:41:43 UTC
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:

    <Import Project="$(MSBuildThisFileDirectory)\SubDirectory\*"/>

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.