Bug 2636 - Intellisense only for some files
Summary: Intellisense only for some files
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 2.8 beta 3
Hardware: Macintosh Mac OS
: Low normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2011-12-25 01:14 UTC by Llorenç Marti
Modified: 2012-01-03 08:58 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 FIXED

Description Llorenç Marti 2011-12-25 01:14:21 UTC
Description of Problem:

Right now i have intellisense capabilities in some files and no intellisense on others.

Steps to reproduce the problem:
1. Open one C# file, test intellisense, and it works autocompleting my function 
2. Open another c# in the same level of the project and no autocompletion for the functions I added via "using UnityEngine;"

Actual Results:

Autocompletion on some files, nothing on others


Expected Results:

Autocompletion and intellisense on all files

How often does this happen? 

Allways

Additional Information:
Comment 1 Mike Krüger 2012-01-03 08:58:55 UTC
The next generation of completion engine will be more stable. 
Stuff like that shouldn't happen there anymore.