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.
Accidentally committing the wrong item from the completion list can be really annoying now, since it can result in importing a namespace. This is annoying for a few reasons:
a) it's not immediately obvious that a namespace has been imported
b) if the bad type is manually backspaced, the import is not removed
c) if Undo is used to remove the namespace, the text editor scrolls so that the caret it right at the bottom of the screen.
Perhaps we could make the namespace importing more explicit, e.g. insert a fully qualified name and then offer a tooltip "press alt-enter to convert to using"?
We are still adding random using statements to peoples source code. Can we fix the implementation so it does not eagerly add useless using statements to the source?
cc'ing alex so he can provide a repro
no we don't - grab a master build.
btw. I would like to have use cases where the import thing did that.