Bug 10860 - Semantic highlighting lost if project reloaded
Summary: Semantic highlighting lost if project reloaded
Status: VERIFIED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
: 11305 ()
Depends on:
Blocks:
 
Reported: 2013-03-03 19:18 UTC by Mikayla Hutchinson [MSFT]
Modified: 2013-03-22 17:16 UTC (History)
3 users (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 Mikayla Hutchinson [MSFT] 2013-03-03 19:18:49 UTC
If a project is reloaded because the project file changes, then semantic highlighting stops working on open files belonging to that project.
Comment 1 Mike Krüger 2013-03-04 05:38:26 UTC
fixed
Comment 2 Jatin 2013-03-08 08:55:45 UTC
Today, with the latest builds:

Xamarin Studio 4.0.2.15
MT 6.2.1.198
MFA 4.6.01058
Xamarin.Mac 1.2.43
Mono 2.10.12

And we have observed that now this issue is not appearing, as now after reopening the project the semantic highlighting remains active.

Hence, closing this issue.
Comment 3 Mike Krüger 2013-03-22 17:16:55 UTC
*** Bug 11305 has been marked as a duplicate of this bug. ***