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.
Data nodes in MSBuild files have excessive nesting, for example
<Command type="Execute" command="../foo.exe" />
This is because MSBuildProjectHandler is using GetXmlString/GetDataNode, which which consider the node to have an outer XML element, and then put that in a property of the same name.
On a related note, this isn't really a good way to handle custom commands. Firstly, properties aren't expected to have XML content. Secondly, it won't work with xbuild. Thirdly, it could conflict with future MS additions. A better solution would be to handle them as MSBuild targets, using the MS extension points.
We are moving away from this model, but we need to keep this double nesting for backwards compatibility.