Bug 5151 - Implicit assembly dependencies should be pulled in
Summary: Implicit assembly dependencies should be pulled in
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: unspecified
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mikayla Hutchinson [MSFT]
: 4810 ()
Depends on:
Reported: 2012-05-17 16:55 UTC by Jonathan Pryor
Modified: 2016-08-03 15:37 UTC (History)
5 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 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.

Related Links:

Description Jonathan Pryor 2012-05-17 16:55:12 UTC
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?
Comment 1 Jonathan Pryor 2012-05-17 16:56:01 UTC
Furthermore, including assemblies into the .apk (e.g. Release builds) have implicit referencing behavior, while fast deployment has explicit reference behavior.
Comment 2 Mikayla Hutchinson [MSFT] 2012-05-17 17:23:54 UTC
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.
Comment 3 Jonathan Pobst 2012-05-18 15:19:04 UTC
Fixed VS's FastDev to have implicit behavior in 55804d056ae2f468dfec93c38e5effaa620f3c91.

MSBuild appears to already do implicit behavior for FastDev.

That just leaves MonoDevelop.
Comment 4 Jonathan Pobst 2012-05-18 15:19:30 UTC
*** Bug 4810 has been marked as a duplicate of this bug. ***
Comment 6 Mikayla Hutchinson [MSFT] 2013-11-06 19:42:53 UTC
This was fixed long ago, we use the list in resolved_assemblies.txt which is generated by the build.