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.
Sometimes the placement of the smart tag is very unintuitive. For example:
The caret is in the assignment expression, but the tag is on the variable:
The caret is in the variable, but the tag is in the assignment operator:
It's not the placement it's the code actions that are a bit too eager giving actions. They should check more restrictive.
That was the case with the old smart tag system (the actions didn't change) - but now it's more visible when that happens.
I'll try to look for specific actions.
btw. the tag marks the point of interrest - therefore it makes sense that it's under the assignment operator in some cases even if the caret isn't there. It says: here you can do something.
->Closing since it's not a bug in the smart tag system, it's the individual actions that should be more sensitive.