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.
Steps to rproduce:
2.Create MonoTouch Single view application.
3.Open Main.cs file.
4.Type any keyword.
5.Auto complete popup appears.
6.Double click any function/variable.
7.Type . after function/variable.
8.No auto complete popup display.
When user type . after selected function/variable,no auto complete popup appears.
Auto complete popup shoud be appears after selecting function/variable.
Please refer attached screenshot.
Created attachment 863 [details]
This is working fine for MonoforAndroid but not for MonoTouch
From the screenshot, and a little of my testing, it seems this is only happening outside the context of a method. Within the body of a method, the autocomplete box seems to work fine.
It's highly possible that in this case the code completion has simply gotten more accurate. There are no valid things to display in this kind of scenario unless the attribute has an inner class like:
public class Foo
public class Bar
In that case it'd be expected and valid to see 'Bar' listed when you press dot. Otherwise it should display nothing.
This also seems to affect declaring new namespaces. You type "namespace " and it gives you a list of completions, but if you choose one and type '.' there is no further completion list presented.
The initial screenshot looks like not a bug and the namespace issue has been resolved in the newresolver branch (where the regression existed), so closing this.
We have tested this issue,this is working fine.