Bug 6756 - Code Completion in Java Binding Project
Summary: Code Completion in Java Binding Project
Status: RESOLVED DUPLICATE of bug 6695
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: 3.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2012-08-29 22:16 UTC by hwrdprkns
Modified: 2012-08-31 11:56 UTC (History)
2 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 hwrdprkns 2012-08-29 22:16:30 UTC

I have recently been able to link an Android library project to Mono For Android project. I would expect that MonoDevelop should be able to have code completion for this binding project since it has the DLL reference handy and seems to compile correctly. 

Problem: No code completion for Java Binding Project

Behavior: I link Binding Project to main project and there is no Code Completion/Intellisense

Expected Behavior: Code completion and the ability to know whether a reference exists for a class that is from the binding project.

Mono For Android: 4.2.5
Comment 1 Mikayla Hutchinson [MSFT] 2012-08-31 11:56:21 UTC

*** This bug has been marked as a duplicate of bug 6695 ***