Flyspray:: Flyspray::Codinion: Recently edited tasks 2018-05-09T06:17:35Z FS#123: Switching back to VS2015, Syntax Highlighting is GONE! 2018-05-09T06:17:35Z 2018-05-08T13:16:58Z

Just purchased a license and have a very unfortunate problem.  Have been using VS2017 and Codinion happily.  Was forced to switch back to VS2015, and now Codinion's highlighting, even in its own configuration dialogs, is kaput.  Uninstalled and reinstalled, no help.

Have attached a couple of screenshots and Codinion logs.  The only VS activity logs are a year old, so they are not included.


Steve Owens
FS#121: My Visual Studio Enterprise 2015 crashes if codinion extension v1.0.1.30 is enabled 2018-04-14T06:35:51Z 2018-04-14T06:35:51Z

I got my VS crashing (Application event logger is reporting devenv.exe crash because of clr.dll stackoverflow) when I open any solution since 11th of Apr 2018. Before this date it was all Ok and I really like extension! After two days of investigation and even reinstall of VS and Windows 10 I found that problem is caused by Codinion extension. It was probably updated on 11th of Apr 2018. Current codinion version is v1.0.1.30

If I disable Codinion then VS opens solutions and I can work fine but if I enable it VS crashes just if I try to open any solution.

Please find attached codinion log files. No "ActivityLog.xml" for VS is available as this is fresh VS installation and I guess no logs are collected by VS. It all loks as pure codinion issue :(

I guess all problem caused by missing assembly. see next log lines

[2018.04.14 09:11:07] [Error] [Codinion.CodinionPackage.OnPackageStartup] System.IO.FileNotFoundException: Could not load file or assembly 'netstandard, Version=, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified.
File name: 'netstandard, Version=, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'

But where I can ge it? Or how can I fix this issue...

FS#120: Highlighting - Syntax coloring for bool operations 2018-04-13T15:27:58Z 2018-04-13T15:27:40Z

I would like boolean operations to have sytax coloring options, mainly true and false comparisions but everything is fair game:

Not Condition

Comparision to non reserved word




Comparision to reserved word

== false

== true

!= false

!= true

FS#119: Highlighting does not work correctly until re-setting colors 2018-04-10T17:44:08Z 2018-04-10T04:47:42Z


I just got the update to and the syntaxt highlighting behaves a little strange:

When I first open a solution most of the colors are the default ones and not the ones I set. Opening the options, changing them to something different and then back fixes it temporarly until I restart VS (where I, by the way, still have the "5 minute open delay" reported in the other bug).

Also the update "killed" my custom colors and did reset them to the default ones (I think because of the dark/light split).


FS#117: Error on code compare in VS 2017 w/ TFS 2018-04-08T17:16:07Z 2018-03-28T13:41:07Z

Hi there.  I'm getting an error when doing a code comparison in VS 2017 using TFS that seems to be generated from Codinion.  ActivityLog.xml file has been attached.

Rick Elliott
FS#118: Extreme delay on solution open and high memory usage 2018-04-05T12:28:45Z 2018-04-05T12:28:45Z

I have VS 2017 and a solution here where Codinion is basically unusable. Loading the solution already takes several minutes instead of seconds if Codinion is enabled (even if all Codinion features are disabled).

In the log is nothing special:

[2018.04.05 13:52:27] [Info]  Codinion ( started.  
[2018.04.05 13:52:27] [Info]  Codinion is up to date. []  

and in the debug-log:

[2018.04.05 13:53:15] [Debug] [Codinion.SyntaxHighlighting.SyntaxHighlightingManager.RegisterClassifier] E:\...\x.cs  
[2018.04.05 13:53:15] [Debug] [Codinion.SyntaxHighlighting.Classifier.CSharp.CSharpClassifierBase.Init] x.cs  
[2018.04.05 13:53:17] [Debug] [Codinion.VisualStudioManagement.TextView.TextViewManager.AddView] Added View:E:\...\x.cs  

If I then enable Enhanced Syntax Highlighting the memory-usage jumps from ~1GB to 2.5GB and VS crashes regularly with out-of-memory exceptions.

The solution has 25 project and a few hundred files and 53k LoC (yes, I need all of them in the solution ;-P) which shouldn't be a problem or cause such high memory usage.

I do NOT have such big problems with some other solutions of equal size.
Why can one solution create such trobles and how can I find out whats causing this and avoid it?

regards & tahnks for your gread work

P.S.: Aside from some minor extensions which should not cause interferences I have the following running: Productivity Power Tools, WebEssentials and ReSharper.


FS#80: Detect Visual Studio Theme 2017-12-31T14:40:38Z 2016-09-20T17:17:10Z

- detect theme changes

-  provide highlighting profiles which switch according to the VS Theme

Martin Topfstedt
FS#115: NULL-Exception by F2 (Rename) 2017-12-10T16:03:27Z 2017-11-24T15:16:08Z

I've found that I get an error if I want to rename a class or value.

The exeption is: NULL-Argument.

The error does not occur when I disable Codinion.

Codinion Version:

Greetings from Austria


Walter N
FS#116: Support for C++ 2017-12-07T20:17:34Z 2017-12-07T20:01:02Z

Martin Topfstedt
FS#114: Syntex highlighting could get broken after file rename 2017-11-21T17:17:29Z 2017-11-08T00:31:48Z

Open a code file.

Rename that file in the Solution Explorer.

The syntax highlight will get broken.

VS 2017 15.4