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.
Description of Problem:
When resolving an unresolved namespace, the resolution is inserted at the wrong spot—it is inserted at the head of the file, with no newline to separate it from the rest of the using declarations.
Steps to reproduce the problem:
1. Open the attached project.
2. Try to resolve the IComparer reference in MyClass.cs by right-clicking and selecting "System.Collections.Generic."
The using declaration is inserted in the wrong spot, as seen in http://screencast.com/t/MjYbuPEniSy.
The using declaration is inserted after the existing using declarations, on a new line.
How often does this happen?
MonoDevelop Beta 2.9.1, OS X 10.7.2.
Created attachment 1006 [details]
Attaching sample project.