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.
I've found two components that cannot be added to project using Visual Studio 2017, because it complains there are missing assemblies.
It seems that download of some components behave as they are incompatible with VS 2017, but they really are.
Try with SharpSerializer, PhotoView, Xamarin.Mobile
There is a workaround, but requires us to have installed Visual Studio 2015.
After component is downloaded we should copy "components\name_of_the_component\lib" folder to our project location.
I believe someone in Xamarin should review all components and add (download) VS 2017 compatibility for them.
I think that I have found the cause of the issue. When installing in VS (in both 2015 and 2017) the csproj is not properly updated.
The assembly reference is added, but the actual component element is not added. When installing the same components in XS/VS4Mac, this element is added:
The XamarinComponentReference item is now correclty added/removed/updated in the .csproj file.