Flyspray:: Wed, 09 May 2018 06:17:35 +0000 Flyspray::Codinion: Recently closed tasks FS#123: Switching back to VS2015, Syntax Highlighting is GONE! Steve Owens Tue, 08 May 2018 13:16:58 +0000 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.


FS#119: Highlighting does not work correctly until re-setting colors Christoph Tue, 10 Apr 2018 04:47:42 +0000 Hi,

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 Rick Elliott Wed, 28 Mar 2018 13:41:07 +0000 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.

FS#80: Detect Visual Studio Theme Martin Topfstedt Tue, 20 Sep 2016 17:17:10 +0000 - detect theme changes

-  provide highlighting profiles which switch according to the VS Theme

FS#115: NULL-Exception by F2 (Rename) Walter N Fri, 24 Nov 2017 15:16:08 +0000 Hy,
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


FS#114: Syntex highlighting could get broken after file rename wmj Wed, 08 Nov 2017 00:31:48 +0000 Open a code file.

Rename that file in the Solution Explorer.

The syntax highlight will get broken.

VS 2017 15.4

FS#108: Enhanced Syntax Highlighting not working for .NET Core / .NET Standard projects Alexandre Machado Wed, 19 Jul 2017 14:19:47 +0000 I'm using Visual Studio Community 2017 and created a .NET Standard Class Library. Although it created a .csproj Project File (instead of "project.json" like VS2015), it does not reference source files (.cs) in it; instead, it dynamically "adds" to the project every existing file in the folder/subfolders. Thus, I guess Codinion isn't working because it needs to know about referenced files. But it would be great if you could manage this case so that we can have Enhanced Syntax Highlighting also for those new framework projects.

FS#37: Highlight "return" statement wmj Tue, 02 Feb 2016 14:07:55 +0000 Is it possible to draw an icon on the left side of the editor (the place we click and create break points) for "return" statements, so it could be easier to spot exit points of long methods?

FS#73: Highlighting for "Syntax Error" Keith Wed, 27 Jul 2016 17:47:27 +0000 Please considering adding custom syntax highlighting for "Syntax Error"

Under Tools > Options > Fonts and Colors > Syntax Error Visual Studio currently only allows the Item Foreground to be changed. 

Having a the option to change the background color, etc.. through Codinion will be an excellent addtion.

Thank you!

FS#77: Feature request: 1, Member type filtering; 2, Sort by type name first, then member name wmj Sat, 20 Aug 2016 01:54:14 +0000 Please add two features to the navigation list.

1, Filtering the members with the types. Is it possible to add some buttons to the left of the textbox above the navigation list?

2, Is it possible to optionally sort the items by type names first, then by member names?