Bug 5731 - Intellisense not working for new APIs
Summary: Intellisense not working for new APIs
Status: RESOLVED DUPLICATE of bug 5558
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 3.0.x
Hardware: Macintosh Mac OS
: High normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-06-19 01:34 UTC by Stuart Carnie
Modified: 2012-06-20 02:03 UTC (History)
4 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 Stuart Carnie 2012-06-19 01:34:41 UTC
Inside IDE, typing UIWindow.Notifications does not show up in intellisense.

Other new APIs, like:

NSObject o;

o.Retai... does not work either.

Navigating to the Assembly Browser does show these APIs are available, and the code compiles fine.
Comment 1 Mike Krüger 2012-06-19 02:02:42 UTC
Which md version ?

Is the reference correctly set  -or are you using transitive references (which compile fine atm, but are incorrect) ?
Comment 2 Mikayla Hutchinson [MSFT] 2012-06-19 02:21:41 UTC
Perhaps the new code completion system did not detect that the framework assemblies had been updated?
Comment 3 Mike Krüger 2012-06-19 02:47:22 UTC
y, we had a bug with .dll updates - but that should've been fixed in 3.0.3.x

Therefore the information about the version is important.
Comment 4 Stuart Carnie 2012-06-19 06:18:48 UTC
I am running MD

Is there anything you want me to run / test to confirm it might be a code completion issue?
Comment 5 Miguel de Icaza [MSFT] 2012-06-19 13:05:05 UTC
Is there a workaround for now to reset the cached assembly completion info that Stuart can use?
Comment 6 Stuart Carnie 2012-06-19 13:06:10 UTC
Couldn't find any obvious files in Caches, etc - would be much appreciated!
Comment 7 Mikayla Hutchinson [MSFT] 2012-06-19 13:10:37 UTC
As a workaround you can delete the code completion caches: ~/Library/Caches/MonoDevelop-3.0/DerivedData
Comment 8 Stuart Carnie 2012-06-19 13:43:00 UTC
Confirmed, thanks!

It was 3:30 AM, so perhaps that is why I missed it in ~/Library/Caches the first time :)
Comment 9 Mike Krüger 2012-06-20 01:35:34 UTC
Did it help to remove the cache ?
Comment 10 Mike Krüger 2012-06-20 01:47:26 UTC
I checked the history - good news - the bug is already fixed. 
Bad news - we didn't ship the fixed version :(

*** This bug has been marked as a duplicate of bug 5558 ***
Comment 11 Stuart Carnie 2012-06-20 02:03:44 UTC
Yes indeed - removing cache resolved the issue.