hicknhack-software / semantic-colorizer Goto Github PK

The tradition of naming constants in ALL_CAPS is becoming less common for consistency's sake, but it would still be nice to have a visual indicator that a member is constant.

Hi,

I wanted to see if I can improve syntax highlighting by using your tool instead of VA's one, which is lacking now. Installed extension, restarted VS, no effect. Disabled VA, no effect. uninstalled VA, restarted VS, no effect. I can help you diagnose if you'd like.

To clarify - I even changed colors to see if that would trigger it to work. All I get is native VS highlighting - gray mess.

Cheers,
Yuriy

There are a couple of minor updates needed for the VSIXManifest to support VS 2019:

https://blogs.msdn.microsoft.com/visualstudio/2018/09/26/how-to-upgrade-extensions-to-support-visual-studio-2019/

No other changes necessary.

I downloaded this to try and emulate a VSCode theme that I like a lot, unfortunately the highlighting does not work. I also tried it on Visual Studio 16.5 prior to 16.7 and had no luck there either.

Would be awesome if Bold worked, but the setting seems to be ignored on SemanticColorizer options.

Hello,

I experience some bugs regarding the colors of keywords since the update.
I've attached a screenshot, so you can see it for yourself.
Any idea what is causing this?

Had some trouble getting the SemanticColorizer to work in my custom VS2017 theme. I tracked it down to the "Identifier" color being set within the Color Theme Editor. If "Identifier" is set to Automatic then everything is OK, but setting a specific color prevents any other colors from being set using SemanticColorizer.

Not sure if it's something that can be worked around, or is worth working around as I'm not entirely sure what the point of the "Identifier" color is, but I thought it was worth bringing up in case anyone else runs in to this problem.

Hello, once again VS updates screwed up my favorite extension!

It seems like these don't apply anymore:

• Sematic Normal Method
• Semantic Property (when used, but it works when declared)

Examples:

1. base.OnNavigatedTo before was the same yellow as in public override async void OnNavigatedTo
2. IsBusy = true before was purple (same color as parameters)

I am using VS 2017 v15.8.7

Any way to restore those colors?
Thanks!

It's missing. If you just download the project and build it will fail on it.

Semantic Colorizer Causes Visual Studio 22 17.9.3 To Hang and Crash. Tested a few times. VS works fine when Semantic Colorizer is uninstalled - but hangs/crashes when it's installed. Is this an issue since VS 17.9.X? Shame since I use the extension and have had to uninstall it.

Would really like to tone down attributes.

I believe there is a conflict with the highlighted colors.
This extension seems to override the foreground colors. I chose white foreground for highlighted definition and reference, but the SEM variable color takes priority and makes it hard to read.

Like title says, just installed v15.7.0 update and semantic doesn't work anymore...

While it's allowed to change color of the struct/classes/enums/interfaces/delegates/type parameters via extension, it looks like that VS will always give it's own settings ("User Types - ..." sections in Options-> Fonts and Colors) a higher priority, unless the color is set to Automatic (?).

If it's true, i think it should be mentioned somewhere in the readme.

When setting a color for a property the word 'public' will be colored in the same color. This only happens with a property, not with any other variable, method etc..

Love your extension! However, I was wondering if there is any way to disable the italic formatting of extension methods?

Thanks!

Like title says, is it possible to have semantic offering different colors for private and public fields?

After the latest update (1.3.1) some of my color codes don't apply anymore.

In particular:

• public keyword on properties: I set it to be bold and orange
  
• Fields: _guide should be green, but another color applies. It's the same I used for types (see screenshot above)
• Methods: I set the to a type of yellow (same as the constructors), but it's showing the same color as types:
  
• out keyword: same problem as public keyword in properties:
  
• Properties: that is not the color i set for properties (should be the same purple)
  

Would it be possible to roll back to the previous version while you investigate?
This is an older screenshot i still had, to show how it's supposed to be:

It's an incredibly valuable tool that makes works so much better, I realize it now that a few colors i was used to are gone :)

I downloaded it and it installed properly but my default colour scheme is very different from the example. Fields are solid red and namespaces are solid green as an example. I'm okay with it not installing properly, I have other plugins and other colour customization so I'm less worried about it installing with the right colours but it would be good if there was some schemes that you can download and apply. Like a dark and light theme for example.

They should be treated as keywords.
I'm using version 1.3.1.

Semantic Colorizer causes a significant delay between hitting keys and the characters appearing in VS 2022. The delay is less in smaller files (but still exists), but can quickly become borderline unusable. In a file of ~200 lines, simply typing out a new property can result in a delay of 10+ seconds from finishing entering the line to VS catching up. I've confirmed that the delay is being caused by Semantic Colorizer by disabling the extension and confirming the delay no longer happens.

Hello there!

I've noticed that there are no ".vsix" installer files for recent releases.
Would it be possible to include it when a new release drops, please? :)

After a recent VS 2022 update, I often get an error bar at the top of Visual Studio 2022 that says: "Feature 'Semantic classification' is currently unavailable due to an internal error." When this happens, colors tend to fail to update, especially when code is commented out.

EDIT:
Below is the stack trace:
StreamJsonRpc.RemoteInvocationException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree') at StreamJsonRpc.JsonRpc.<InvokeCoreAsync>d__1511.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Threading.Tasks.ValueTask1.get_Result() at Microsoft.CodeAnalysis.Remote.BrokeredServiceConnection1.d__201.MoveNext() RPC server exception: System.ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree') at Microsoft.CodeAnalysis.CSharp.CSharpCompilation.GetSemanticModel(SyntaxTree syntaxTree, Boolean ignoreAccessibility) at Microsoft.CodeAnalysis.Document.GetSemanticModelAsync(CancellationToken cancellationToken) at Microsoft.CodeAnalysis.Shared.Extensions.DocumentExtensions.GetRequiredSemanticModelAsync(Document document, CancellationToken cancellationToken) at Microsoft.CodeAnalysis.Classification.AbstractEmbeddedLanguageClassificationService.AddEmbeddedLanguageClassificationsAsync(Document document, TextSpan textSpan, ClassificationOptions options, SegmentedList1 result, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.Classification.AbstractClassificationService.AddClassificationsInCurrentProcessAsync(Document document, TextSpan textSpan, ClassificationType type, ClassificationOptions options, SegmentedList1 result, CancellationToken cancellationToken) at Microsoft.CodeAnalysis.Remote.RemoteSemanticClassificationService.<>c__DisplayClass20_0.<<GetClassificationsAsync>b__0>d.MoveNext() --- End of stack trace from previous location --- at Microsoft.CodeAnalysis.Remote.RemoteWorkspace.<>c__DisplayClass9_01.<g__ProcessSolutionAsync|1>d.MoveNext()
--- End of stack trace from previous location ---
at Microsoft.CodeAnalysis.Remote.RemoteWorkspace.RunWithSolutionAsync[T](AssetProvider assetProvider, Checksum solutionChecksum, Int32 workspaceVersion, Boolean updatePrimaryBranch, Func2 implementation, CancellationToken cancellationToken) at Microsoft.CodeAnalysis.Remote.RemoteWorkspace.RunWithSolutionAsync[T](AssetProvider assetProvider, Checksum solutionChecksum, Int32 workspaceVersion, Boolean updatePrimaryBranch, Func2 implementation, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.Remote.BrokeredServiceBase.RunWithSolutionAsync[T](Checksum solutionChecksum, Func2 implementation, CancellationToken cancellationToken) at Microsoft.CodeAnalysis.Remote.BrokeredServiceBase.RunServiceImplAsync[T](Func2 implementation, CancellationToken cancellationToken)
`

Hi, sorry for posting this here, but I cannot find information how to change the colors in this extension.
I also noticed that colors are different in the extension and in the advertising screenshot (I kinda like ones from the screenshot better).
Can I somehow change them to match ones in the screenshot?

Thanks again for this amazing extension. It works absolutely perfect ;)

However, it does not highlight events in C# code. Would you please add support for it?

Sample code:

class Test
{
    // TestEvent should be able to be highlighted
    event Action TestEvent;
}

This is related to #23 I assumed it was the same issue as the color issues happened on the same release and several people commented on them in that issue specifically for VS 2015.

Field colors, looks like normal method colors as well, possibly enums, and possibly others all fail to be colored.

I just noticed it doesn't work. I see that 1.2 came yesterday, it must auto updated and stopped working.

Hello is it possible to roll back?
I had this extension on "Automatically update", and from today almost all my color settings are gone.
Yesterday everything was perfect.

Thanks

I just upgraded and I cannot get Semantic colorizer to work in Visual Studio 2019. The stupid default syntax colorizer seems to block settings from this addon. IS there any way around this? Disabling advanced setting "Use enhanced colors for c# and basic" did nothing. Still the same ugly default colors used by visual studio. I can change the default colors but they don't have as many options as your plugin. Is this an issue with Visual Studio itself? It seems like it might be an issue with VS itself. Guess I will have to use 2017 until this is fixed.

Since the new version (12/16/2016) SemanticColorizer stopped working. I can't find it under "Fonts and Colors" tab, nor in any other window. It shows as enabled in the "Extensions and Updates" window, but is it? Maybe my configs are wrong?