Bug 10064 - Tooltip on method invocation with incorrect arguments is not useful
Summary: Tooltip on method invocation with incorrect arguments is not useful
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 4.0
Hardware: PC Mac OS
: Normal enhancement
Target Milestone: (C7)
Assignee: Mike Krüger
Depends on:
Reported: 2013-02-05 17:40 UTC by Mikayla Hutchinson [MSFT]
Modified: 2015-05-18 01:23 UTC (History)
1 user (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 Mikayla Hutchinson [MSFT] 2013-02-05 17:40:23 UTC
If I have a method invocation with a correct name but incorrect arguments, the tooltip is not useful, it just shows "Unknown resolve error".

Ideally if a method with that name exists, it would show an "Arguments do not match method" error, with the arguments of the method, so the user would know how to fix the arguments.

It would also be nice if semantic highlighting highlighted unresolved methods.
Comment 1 Mike Krüger 2013-02-06 01:15:24 UTC
Atm nrefactory doesn't really support semantic error information - but it's on our todo list.
Comment 2 Mike Krüger 2015-05-18 01:23:37 UTC
The roslyn resolver now marks semantic errors on the fly.