Bug 5321 - Incorrect syntax colouring after editing on second machine.
Summary: Incorrect syntax colouring after editing on second machine.
Status: RESOLVED DUPLICATE of bug 4866
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 3.0.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-05-25 05:55 UTC by John
Modified: 2012-05-25 11:48 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 John 2012-05-25 05:55:35 UTC
C#. Windows 7. MonoDevelop v3.0.2 and earlier versions.


1) Edit files on machine A. Close project.
2) Copy to machine B.
3) Edit files. Close project whilst some files are open.
4) Copy back to machine A.
5) Open project. 

The files that are open have incorrect syntax colouring. (Method parameters are coloured red.) 

If I delete the machine specific completion.cache in AppData between steps 4 and 5 the problem does not occur. So I think it is a problem with not updating the cache for files opened at start-up.
Comment 1 Mikayla Hutchinson [MSFT] 2012-05-25 11:48:00 UTC
This is fixed in master, which will be released as 3.2.

*** This bug has been marked as a duplicate of bug 4866 ***