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 5035 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
I've tracked down a build bug in MonoMac down to a difference in variable scoping between xbuild and msbuild.
It appears that when you call CallTarget, you loose variable scope. Compare the two attached results files in the attached zip file. I believe msbuild is doing the right thing and xbuild isn't.
Created attachment 1862 [details]
Example of problem.
We currently do not have plans to support much more beyond the basics of xbuild that are used by MD.
I've discovered a similar bug and provided a patch (attached in bug 15431) - you can try it out and see if it fixes your problem.
I believe we encountered this problem as well. In our particular case, we're copying database vendor ADO drivers to the output directory. It's not a straight forward copy operation as different drivers need to be copied to different directories depending on their bitness (x86 vs x64) and the project type (library vs. web application).
We got this working in MSBuild, but it fails with XBuild. As the other commenters note, XBuild seems to lose the scope when executing the CallTarget task.
Same issue. Anyone fixing it?
I've got a simpler example of exactly this bug. Refusing to fix it is pretty much stating that xbuild is being depricated.
This issue will prevent any kind sensible build project.
Created attachment 9117 [details]
Created attachment 9118 [details]
place the .target file and the .proj file in the same folder, xbuild call-issue.proj and observe the output:
Fix the bug or deprecate xbuild, anything else is being dishonest.