Codinion

Open a code file.

Rename that file in the Solution Explorer.

The syntax highlight will get broken.

VS 2017 15.4

The "Highlight search results" function is conflicting with VSColorOutput, which also highlights the output window.

Reproduction:

1, Install VSColorOutput and Codinion.

2, Press Ctrl+H in the editor to display the search and replace dialog.

3, Hit the "Replace All" button to replace multiple text.

VS will crash after step 3.

Is it possible to add a highlight option for locked regions (maybe adding a background inside the {} of the lock body)?

lock (syncRoot) {

}

I downloaded the zipped code from this place: https://github.com/tunnelvisionlabs/InheritanceMargin

And then opened the solution with VS 2017 (latest build).

The Enhanced Syntax Highlighting was not working at all.

Please check to see whether you can reproduce the bug and fix the problem.

I'd got both VS 2015 update 3 and VS 2017 RTM on my machine.

After installing the latest version of Codinion, the highlighting function did not work at all on both instances.

The patch build in this issue was working fine, but the new build failed on both versions: http://flyspray.codinion.com/index.php?do=details&task_id=87&status%5B0%5D=

I have both VS2015 and VS 2017 RC installed on my computer (both of them were upgraded to the latest versions).

I saw TWO codinion instances, one versioned 4595 and the other versioned 4703, on my VS 2015 extension manager (the same to my VS 2017 RC).

After disabling the 4595 one, the rest one became normal.

A NullReferenceException was caught and logged into the ActivityLog.xml

at Codinion.SyntaxHighlighting.Classifier.CSharp.CSharpClassifierBase.GetClassificationSpansInternal(SnapshotSpan span)

at Codinion.SyntaxHighlighting.Classifier.ClassifierBase.GetClassificationSpans(SnapshotSpan span) at Microsoft.VisualStudio.Text.Classification.Implementation.ClassifierTagger.<GetTags>d__5.MoveNext()

at Microsoft.VisualStudio.Text.Tagging.Implementation.TagAggregator`1.<GetTagsForBuffer>d__38.MoveNext()

When VS 2017 RC was started, a dialog looked like the following attachment appeared.

In the stack trace, I found Codinion.

The same dialog once happened in my VS 2015 installation with the stable version of Codinion.

VS could not be started without the "/safemode" parameter or Codinion uninstalled afterward.

While I was editing code files with #if...#else...#endif instructions, the highlighting feature became not working after inserting and deleting some characters.

Please check to see whether this issue could be fixed.

Recently I'd reinstalled the Windows and of cource, Visual Studio 2015 too.

When I installed the latest Codinion, it by default used the dark theme.

I tried to select the light theme from the drop down box, but it did not work.

When the selection was changed, nothing happened; after closing and reopening the Options dialog, the default theme box went back to the Dark theme.

How could I quickly switch to the Light theme?

The interpolated strings introduced in c# 6 were not using the highlighting definitions of strings.

For instance:

Console.Write($"Now is {DateTime.Now}.");

The "Now is " and the following period was not using the string color.

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?

Please sort the recently used items in the jump list and make the most recently opened project placed ahead of (or optionally below) the older ones.

I'd just enabled the JumpList with the Recent Items option checked.

The JumpList did not show Start Up Modes unless the Recent Items option was unchecked. Is it possible to show both the Start Up Modes and Recent Items at the same time?

Recently I was experiencing crashes of VS 2015, both in update 2 and update 3 (upgraded the day before yesterday).

I reported this to the VS support team and they replied that "I have looked over telemetry and screenshot collected with your feedback item and I think I know which extension is causing your crashes. Codinion appears in several of the stack traces of crashes."

After disabling Codinion, the crashes were gone.

I examined the Codinion\Logs folder and the ActivityLog.xml, no relative information was found.

Please help fix this. I could not work well without Codinion.

Recently I was experiencing crashes of VS 2015, both in update 2 and update 3 (upgraded the day before yesterday).

I reported this to the VS support team and they replied that "I have looked over telemetry and screenshot collected with your feedback item and I think I know which extension is causing your crashes. Codinion appears in several of the stack traces of crashes."

After disabling Codinion, the crashes were gone.

I examined the Codinion\Logs folder and the ActivityLog.xml, no relative information was found.

Please help fix this. I could not work well with Codinion.

In the screenshot, the upper #if was not highlighted because it did not have an "#else" directive.

Please take a look at the screenshot. The upper #if was not applied with highlight, but the lower one does. The diffrence was that the upper one did not has a "#else" directive.

Could you please modify the vsix file to make it support the upcoming VS 15?

I found that those two types of projects were not applying syntax highlighting, although they use C# programming languages.

For instance, take a look at this project: https://github.com/StackExchange/dapper-dot-net

And the SQL CLR Projects issue could be verified by creating a new SQL Server CLR project.

There are two issues in the latest beta.

Reproduction:

1, Create a new WinForm project.
2, Add a control, for instance, a button named "button1", onto the Form from the designer.
3, Switch to the code view and type "button1" in the code window.
Issue 1: The "button1" will not be highlighted.
4, Type the following:

button1.Click +=

5, Press the Tab key on the keyboard to create the event handler for the Click event. VS will complete the code as:

button1.Click += Button1_Click;

And a method named "Button1_Click" will be created below.
Issue 2: "Button1_Click" on the above method is not highlighted.

Some syntax highlight on certain types or members, such as extension method calls, method calls, property references, etc. would not be effective after upgrading NuGet packages.

Some syntax highlight on certain types or members, such as extension method calls, method calls, property references, etc. would not be effective after upgrading NuGet packages.

Is it possible to highlight pre-processor directives such as the following:

#define VARIABLE

#region REGION DESCRIPTIONS HERE
#endregion

#if CONDITION
#elif CONDITION
#endif

#progma warning disable/restore CODE
#endprogma

Since those directives takes a line, is it possible to apply the style to the whole line rather than just the characters?

Hello,

I've just upgraded to the last beta. The theme file corruption issue and inconsistency issues were not yet fixed.

Corruption issue:
The new theme file has gotten somehow messed up with two encodings, apparently UTF-8 and UTF-32.
The theme file serialization part shall have some problem.
And there's no need to save the theme file in UTF-32. UTF-8 will do.

Inconsistency issue:
The new beta saves the theme file in XML format.
But the Settings.xml file still references to the old binary format.
Thus the new theme won't get loaded after theme changes.

I changed the string highlight rule to color black and use the Verdana font, but it was deactivated after restarting VS.

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?

Hello,

I am using a Chinese operating system, and I found that the syntax font family names are not displayed as the system's Fonts folder.

The following statement could be used to list all GDI+ supported fonts in the system and the names are displayed respecting locale settings:

new System.Drawing.Text.InstalledFontCollection().Families

In the following code, const variables "C" and "D", defined in a constructor, were not using the any rule of systax highlighting.

class A {
const string B = "_b";
static A () {
const string C = "e";
const string D = "f";
}
}

I set up "static" types and members to use a dashed underline.
After the configuration, the "System" in the "using System;" statement, and "MyNS" in "namespace MyNS" also been underlined with a dash. Since the "System", "MyNS" should not be classified as "static" types, this may be a bug.

Is it possible to use different fonts for different rules?
For instance, strings are rendered with Times New Roman, and constants rendered with Arial Black, etc..

Is it possible to highlight extension methods?

Change the display settings and set the DPI to 125%, the banner will look blurry.

I set the font size for declarations of types or members, but it was not used.
Please fix it.

I downloaded the new beta and found that I did not activate the "keyword" rule of syntax highlighting, leaving it as default, but its color was still used.

Multiline strings like below could not be highlight correctly with the configured syntax color:

var string = @"strings
multiline
";