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.
Created attachment 19836 [details]
Intellisense does not work for types referenced from Android Java Bindings Library projects when using a project reference. Intellisense issue only, project builds work.
Possible dupe of old bug report bug #17857, but that is for VS Extensions. I have discovered the same issue in Xamarin Studio on the Mac (C9), as well as Visual Studio for Mac. It works as expected on the C8SR1 builds.
## Steps to reproduce
1. Open the attached test project and build solution using either XS on Alpha/Beta (C9) or VS for Mac Preview.
2. Open the MainActivity.cs file and inspect the using statements at the top and the statement on line 22
Expected result: No red underline on Com.Squareup.Picasso or on Picasso.With call on line 22.
Actual result: Com part of Com.Squareup.Picasso is underlined in red indicating that the namespace is unresolved and there is a red line under Picasso in the Picasso.With call on line 22 with a hover message that "The name Picasso does not exist in the current context."
A workaround is to reference the binding assembly directly instead of using a project reference.
I see the same issue in the Visual Studio extensions for both Android (bug #17857) and iOS (bug #42448).
I also see a very similar issue with iOS binding projects in VS for Mac and XS C9, will file a separate bug report for that.
## Regression status
This is a regression in C9 and Vs for Mac
GOOD: XS 6.1.5
BAD: XS 6.2
BAD: VS for Mac Version Preview 3 (7.0 build 1077)
=== Xamarin Studio Enterprise ===
Version 6.2 (build 1812)
Installation UUID: ceaba76c-db06-4fbd-b326-f69ea53c3e01
Mono 4.8.0 (mono-4.8.0-branch/9ac5bf2) (64-bit)
GTK+ 2.24.23 (Raleigh theme)
Package version: 408000489
=== NuGet ===
=== Xamarin.Profiler ===
'/Applications/Xamarin Profiler.app' not found
=== Apple Developer Tools ===
Xcode 8.2.1 (11766.1)
=== Xamarin.Mac ===
Version: 18.104.22.1681 (Visual Studio Enterprise)
=== Xamarin Inspector ===
Build date: Tue, 14 Feb 2017 15:22:42 GMT
=== Xamarin.Android ===
Version: 22.214.171.124 (Visual Studio Enterprise)
Android SDK: /Users/jongoldberger/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
4.0.3 (API level 15)
4.1 (API level 16)
4.2 (API level 17)
4.3 (API level 18)
4.4 (API level 19)
5.0 (API level 21)
5.1 (API level 22)
6.0 (API level 23)
7.0 (API level 24)
SDK Tools Version: 25.2.5
SDK Platform Tools Version: 25.0.3
SDK Build Tools Version: 25.0.2
Java SDK: /usr
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)
Android Designer EPL code available here:
=== Xamarin Android Player ===
Location: /Applications/Xamarin Android Player.app
=== Xamarin.iOS ===
Version: 10.4.0.121 (Visual Studio Enterprise)
Build date: 2017-02-10 12:10:51-0500
=== Build Information ===
Release ID: 602001812
Git revision: 33e69e5df3c62c2c4084cf1b8de26fda93c5e843
Build date: 2017-02-09 12:18:09-05
Xamarin addins: 984f6bd4e491490d1cdf37352594300dab2b1597
Build lane: monodevelop-lion-cycle9
=== Operating System ===
Mac OS X 10.12.3
Darwin Jons-MacBook-Pro.local 16.4.0 Darwin Kernel Version 16.4.0
Thu Dec 22 22:53:21 PST 2016
=== Enabled user installed addins ===
Addin Maker 1.3.2
Prism Template Pack 1.5
*** This bug has been marked as a duplicate of bug 52553 ***