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.
Question: Should implicit assembly dependencies be pulled in, or should we require that the Application project explicitly reference all assemblies to distribute in the app?
See the epic thread!
Pro to implicit dependencies:
* It's what VS and MonoTouch do
Con for implicit dependencies:
* It's hard to see at a glance which assemblies will be packaged in the .apk
Does that actually matter?
Furthermore, including assemblies into the .apk (e.g. Release builds) have implicit referencing behavior, while fast deployment has explicit reference behavior.
Why doesn't fastdev use the linker's resolver to find the full set of assemblies the same way that release builds do, instead of requiring/using local copy? Then you can remove the otherwise pointless local copy step from the build code, as described in bug 4810.
Fixed VS's FastDev to have implicit behavior in 55804d056ae2f468dfec93c38e5effaa620f3c91.
MSBuild appears to already do implicit behavior for FastDev.
That just leaves MonoDevelop.
*** Bug 4810 has been marked as a duplicate of this bug. ***
This was fixed long ago, we use the list in resolved_assemblies.txt which is generated by the build.