Bug 6193 - Code issues spanning multiple lines are displayed incorrectly
Summary: Code issues spanning multiple lines are displayed incorrectly
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Linux
: High normal
Target Milestone: ---
Assignee: Mike Krüger
: 6744 ()
Depends on:
Reported: 2012-07-19 09:21 UTC by Simon Lindgren
Modified: 2012-08-31 03:56 UTC (History)
2 users (show)

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:

Description Simon Lindgren 2012-07-19 09:21:00 UTC
For example this code:

class A
	void F ()
		string s = null;
		string s2 = s != null ? s
			: "";

There is a suggestion to convert the ternary operator usage to the null-coalescing instead. This works fine when the operator spans one line, but not when it spans multiple lines.

The suggestion underline is instead displayed from the end of the first line of the operator to the beginning of the same line. Hovering over the text does not show a tooltip like it usually does, and there is no way to invoke the code action to apply the suggested change.
Comment 1 Mike Krüger 2012-08-30 04:24:46 UTC
*** Bug 6744 has been marked as a duplicate of this bug. ***
Comment 2 Mike Krüger 2012-08-30 04:26:00 UTC
Upping that issue because it's really ugly when working with source analysis enabled.
Comment 3 Mike Krüger 2012-08-31 03:56:10 UTC