Bug 1278 - [2.8] sintax highlight
Summary: [2.8] sintax highlight
Status: RESOLVED INVALID
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2011-10-05 18:11 UTC by Llorenç Marti
Modified: 2011-10-06 01:00 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:
RESOLVED INVALID

Description Llorenç Marti 2011-10-05 18:11:15 UTC
Description of Problem:

Class names doesnt have a correct highlight

Steps to reproduce the problem:
1. Open MD 2.8
2. See any class or any type(semantic), neither have his name colored


Actual Results:

The types (semantic) names are black, when Visual Studio scheme says that these names needs to be colored in clear-blue.

Expected Results:

All the types(semantics) to have the color in Visual Studio scheme

How often does this happen? 

All time

Additional Information:
Comment 1 Mikayla Hutchinson [MSFT] 2011-10-05 19:08:45 UTC
Semantic highlighting has never been enabled by default, because it was slow and buggy. Since it was causing serious problems for people who enabled it, we temporarily removed it.

We are working on a new type resolver that will make semantic highlighting much more performant and reliable. We will then enable it by default.
Comment 2 Mike Krüger 2011-10-06 01:00:46 UTC
That feature got disabled in 2.8 because of internal problems caused by incompatible ast representations. 

But semantic highlighting in 2.8 has no checkbox for semantic highlighting anymore - that's why I close that one.

Somantic highlighting will be back in the next major release.