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 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.
Created attachment 5774 [details]
VS Solution that replicates issue
I'm seeing a strange issue with Xamarin.iOS projects in VS 2012 / 2013 (happens in both).
Basically I have this:
MainApp -- refs --> Assembly A -- refs --> Assembly B
When I debug this app, I get a file not found exception when Assembly B is accessed. Sure enough, Assembly B is not included in the app package that is deployed to the simulator on my Mac build host.
I have reproduced this behavior in a simple test app.
If I build and run the same project from the Mac host / Xamarin Studio, then Assembly B is included correctly and everything works.
If I manually add a reference to Assembly B from the MainApp, then Assembly B gets included in the package sent over to the build host.
Additionally, I reproduced the same issue using SQLite from the component store.
MainApp -- refs --> DataAccess Assembly -- refs --> SQLite.dll
In this case, SQLite.dll is not included in package. If I also add the SQLite component to the main app (even though it's not directly used there) the dll gets packaged correctly.
I'm attaching a VS solution that duplicates this behavior.
Windows 8.1 / Visual Studio 2013, Xamarin.iOS 7.0.4, Stable Channel, Mavericks running on build host.
This is fixed in the beta version of the extension, 1.10, to be released in the near future.