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.
See repro of how I try to create an instance of NSString:
"var foo = NSSt" works
"string bar = new NSStr" does not.
Note that the eventual idea is to write this:
"string var = new NSString (<intptr>).ToString ();"
Hm, that's a good point. It's an odd pattern, but it's valid C#, so the completion engine can't really filter the types there at all.
I think it should pre-select "string" in the above sample (but still list all the other types).
Well, selecting the exact type "string" is what it does already, it can still do this in suggestion mode although the selection will not be solid.
Another idea, IIRC we currently filter to all valid subtypes, maybe we could keep this filtering available by categorizing the list - subtypes vs. all other types?
fixed - the categorizing was a good idea btw.
(Even if I think I will not use it much)