Bug 12095 - How can we check feature "New smart tag system for code actions"?
Summary: How can we check feature "New smart tag system for code actions"?
Status: VERIFIED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0
Hardware: PC Mac OS
: --- normal
Target Milestone: 4.0.9 (from master)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-05-03 13:06 UTC by Saurabh
Modified: 2013-06-24 16:18 UTC (History)
1 user (show)

Tags:
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:
Status:
VERIFIED FIXED

Description Saurabh 2013-05-03 13:06:14 UTC
We are not sure how to check New smart tag system for code actions using X.S 4.0.5 (build 2)?

This is in the release notes:
New smart tag system for code actions
Comment 1 Mikayla Hutchinson [MSFT] 2013-05-03 13:49:52 UTC
If you enable source analysis in Preferences -> Text Editor ->Source analysis, you'll see a little blue tags on the document if code actions are available at the current location.
Comment 2 Saurabh 2013-05-03 14:16:10 UTC
We are able to do this using step which are mentioned in Comment#1
Comment 3 PJ 2013-06-24 16:18:55 UTC
This bug was marked as fixed for Xamarin Studio 4.0.9, which is currently in the beta channel. Try it out!