Bug 9144 - Code completion completely broken for MonoTouch bindings projects.
Summary: Code completion completely broken for MonoTouch bindings projects.
Status: RESOLVED DUPLICATE of bug 6719
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: 6.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-12-27 14:51 UTC by kenny goers
Modified: 2012-12-27 17:04 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED DUPLICATE of bug 6719

Description kenny goers 2012-12-27 14:51:38 UTC
When adding a project reference to a Bindings project from a "normal" MonoTouch project, the code completion doesn't work, in that when you use the types in the bindings projects, they are generally red (as in undefined) and methods and properties won't appear for completion.  This despite being able to open the assembly refrenced and seeing the propertyies and methods.  

This happens in EVERY project that references and then tries to use a bindings project.
Comment 1 Mikayla Hutchinson [MSFT] 2012-12-27 17:04:53 UTC

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