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 on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I am not sure how files automatically add in folder using wildcard?
X.S 4.0.5 (build 2)
To give context for jeff, this is in the release notes:
> Added support for file wildcards in project files (for example, to include all files in a directory).
I actually don't know anything about this (I think it involves something like using * in the .csproj files).
I'll let lluis answer this :-)
In a .csproj file, usually you have a list of files to be built, for example:
<Compile Include="Foo.cs" />
<Compile Include="Bar.cs" />
You can now use wildcards to include several files at once, for example:
<Compile Include="*.cs" />
The special wildcard "**" can be used to recurse directories. For example:
<Compile Include="src/**/*.cs" />
will include all files with extension .cs in the 'src' directory and all its subdirectories.
Notice that MonoDevelop has no UI for specifying wildcards. The wildcards have to be specified by manually editing the .csproj file. MonoDevelop should show all included files in the solution tree.
We need to add unit tests for this.
We have tried instructions which are mentioned in Comment#3 and we are successfully able to get dragged file in solution after editing .csproj manually.
Changing the status of this bug to Verified.