Add possibility to using strikethrough and underline font

Need to cleanup the display names of classifications:

CoCo vs15: "CoCo static method name" => "Static method"
CoCo vs14: "Static method name" => "Static method"
...

• Check that a new constructions in c# 8 are being supported or append supporting of them
• Investigate constructions that can be classified as a new classifications

Will be good to add possibility to prohibit classification of item, which will allow to choose classify items or not that are already classified in the Visual Studio, look at the issue #24.

Hi, when you check the Bold checkbox on Coco Format..., nothing happens.

When I open an F# project in Visual Studio 2017, I get an error dialog indicating that an exception has occurred, and to check the ActivityLog.xml file for details. The file contains several dozen of the following error:

System.NullReferenceException: Object reference not set to an instance of an object.
at CoCo.EditorClassifier.GetClassificationSpans(SnapshotSpan span)
at Microsoft.VisualStudio.Text.Classification.Implementation.ClassifierTagger.d__5.MoveNext()
at Microsoft.VisualStudio.Text.Tagging.Implementation.TagAggregator`1.d__39.MoveNext()

Possibly, the classification should not be happening on F# projects and a language filter is needed?

I've recently reinstalled the VS and must manually reconfig my CoCo presets. As the theme options grow, there should be a way to export and import preset files.

After installing the extension and restarting VS (2017), all of the "CoCo format" colors defined in Tools / Options / Environment / Fonts and Colors are set to "default". I'd suggest having them initially default to some set color scheme like in the example screen shots.

(An initial peek at the code didn't reveal any pre-set defaults, so I assume this isn't simply a bug, but by all means correct me if I'm wrong!)

Currently CoCo supports bold font for classifications but supporting can be extended to the other weights.

I downloaded the source code and I have tried to build it by using MVS 2017, but it gives me the following error:

The "GetDeploymentPathFromVisxManifest" task failed unexpectedly ...

Is anyone familiar with this error?

Need to add a posibility to reset (perhaps for one of classifications or for all of them) options back to default from CoCo/Classifications option page

So we could configure them at one place and much easier (with hex color input).

I assume that the supporting of F# can be done using FSharp.Compiler.Service, if so it would be nice to release it

I encounter regular crashes of Coco in Visual Studio 2017.
The error mainly occurs if i open files other then Cs-files (i.e. rdlc files, xml-files,....)

So here are the key data:
CoCo-Version 3.0.0
Visual Studio Version: Visual Studio 2017 Enterprise, V15.9.11

Error (logged in ActivityLog.xml):

System.AggregateException: One or more errors occurred. System.NullReferenceException: Object reference not set to an instance of an object. at CoCo.Analyser.VisualStudioExtensions.GetLanguage(ITextBuffer buffer) at CoCo.QuickInfo.QuickInfoSource..ctor(ITextBuffer textBuffer, IReadOnlyDictionary2 quickInfoOptions, ITextDocumentFactoryService documentFactoryService)
at CoCo.Providers.QuickInfoProvider.<>;c__DisplayClass4_0.b__0()
at Microsoft.VisualStudio.Utilities.PropertyCollection.GetOrCreateSingletonProperty[T](Object key, Func1 creator) at CoCo.Providers.QuickInfoProvider.TryCreateQuickInfoSource(ITextBuffer textBuffer) at Microsoft.VisualStudio.Language.Intellisense.Implementation.AsyncQuickInfoSession.CreateSources(JoinableTaskContext joinableTaskContext, IEnumerable1 orderedSourceProviders, ITextBuffer textBuffer, IList1 failures) --- End of inner exception stack trace --- at Microsoft.VisualStudio.Language.Intellisense.Implementation.AsyncQuickInfoSession.<UpdateAsync>d__32.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Language.Intellisense.Implementation.AsyncQuickInfoPresentationSession.<UpdateAsync>d__5.MoveNext()&#x000D;&#x000A;---> (Inner Exception #0) System.NullReferenceException: Object reference not set to an instance of an object. at CoCo.Analyser.VisualStudioExtensions.GetLanguage(ITextBuffer buffer) at CoCo.QuickInfo.QuickInfoSource..ctor(ITextBuffer textBuffer, IReadOnlyDictionary2 quickInfoOptions, ITextDocumentFactoryService documentFactoryService)
at CoCo.Providers.QuickInfoProvider.<>c__DisplayClass4_0.b__0()
at Microsoft.VisualStudio.Utilities.PropertyCollection.GetOrCreateSingletonProperty[T](Object key, Func1 creator) at CoCo.Providers.QuickInfoProvider.TryCreateQuickInfoSource(ITextBuffer textBuffer) at Microsoft.VisualStudio.Language.Intellisense.Implementation.AsyncQuickInfoSession.CreateSources(JoinableTaskContext joinableTaskContext, IEnumerable1 orderedSourceProviders, ITextBuffer textBuffer, IList1 failures)

Currently presets are not ordered in the CoCo/Presets page. Would be useful if the will be sort by alphabetical order.

Will be good to add possibility to classify item as on of others or just don't classify it.
This opens way to classify items or ignore them classifications that already classified in the Visual Studio, look at the issue #24.

Also, need to come up with a design which will marks items in the cycle with the current selection in the "Classify as" option or as another posibility just hide items in"Classify as" which build cycle with the current item.

Would be nice if a text in the quick info will classify as in the text editor in the first approximate

• Annotate
• Code files which are not included to solution
• Plain text files which contain a code

Visual Studio 2017 version 15.8.1
CoCo version 2.1.0

  <entry>
    <record>2488</record>
    <time>2018/08/27 12:42:50.769</time>
    <type>Error</type>
    <source>Microsoft.VisualStudio.ComponentModelHost.VsShellComponentModelHost</source>
    <description>Exception occurred while loading assembly CoCo, Version=2.1.0.0, Culture=neutral, PublicKeyToken=null: System.IO.FileNotFoundException: Could not load file or assembly &apos;CoCo, Version=2.1.0.0, Culture=neutral, PublicKeyToken=null&apos; or one of its dependencies. The system cannot find the file specified.&#x000D;&#x000A;File name: &apos;CoCo, Version=2.1.0.0, Culture=neutral, PublicKeyToken=null&apos;&#x000D;&#x000A;   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark&amp; stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)&#x000D;&#x000A;   at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark&amp; stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)&#x000D;&#x000A;   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark&amp; stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)&#x000D;&#x000A;   at System.Reflection.Assembly.Load(AssemblyName assemblyRef)&#x000D;&#x000A;   at Microsoft.VisualStudio.ExtensibilityHosting.FaultCatchingAssemblyLoader.&lt;&gt;c__DisplayClass17_0.&lt;LoadAssembly&gt;b__0(AssemblyName assemblyNameParam)&#x000D;&#x000A;&#x000D;&#x000A;WRN: Assembly binding logging is turned OFF.&#x000D;&#x000A;To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.&#x000D;&#x000A;Note: There is some performance penalty associated with assembly bind failure logging.&#x000D;&#x000A;To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].&#x000D;&#x000A;.;vs.platform.extensibilityhosting.assemblyloadexception.AssemblyFullName=CoCo, Version=2.1.0.0, Culture=neutral, PublicKeyToken=null;vs.platform.extensibilityhosting.assemblyloadexception.AssemblyPath=file:///C:/USERS/STEVEC/APPDATA/LOCAL/MICROSOFT/VISUALSTUDIO/15.0_2120162E/EXTENSIONS/AMWVN5H4.ZCH/CoCo.dll;vs.platform.extensibilityhosting.assemblyloadexception.FusionLogEntry=WRN: Assembly binding logging is turned OFF.&#x000D;&#x000A;To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.&#x000D;&#x000A;Note: There is some performance penalty associated with assembly bind failure logging.&#x000D;&#x000A;To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].&#x000D;&#x000A;;vs.platform.extensibilityhosting.assemblyloadexception.ExceptionType=System.IO.FileNotFoundException;vs.platform.extensibilityhosting.assemblyloadexception.ExceptionMessage=Could not load file or assembly &apos;CoCo, Version=2.1.0.0, Culture=neutral, PublicKeyToken=null&apos; or one of its dependencies. The system cannot find the file specified.;vs.platform.extensibilityhosting.assemblyloadexception.ExceptionStackTrace=   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark&amp; stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)&#x000D;&#x000A;   at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark&amp; stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)&#x000D;&#x000A;   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark&amp; stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)&#x000D;&#x000A;   at System.Reflection.Assembly.Load(AssemblyName assemblyRef)&#x000D;&#x000A;   at Microsoft.VisualStudio.ExtensibilityHosting.FaultCatchingAssemblyLoader.&lt;&gt;c__DisplayClass17_0.&lt;LoadAssembly&gt;b__0(AssemblyName assemblyNameParam)&#x000D;&#x000A;</description>
  </entry>
  <entry>
    <record>2489</record>
    <time>2018/08/27 12:42:50.771</time>
    <type>Error</type>
    <source>Microsoft.VisualStudio.ComponentModelHost.VsShellComponentModelHost</source>
    <description>A MEF Component threw an exception at runtime: System.IO.FileNotFoundException: Could not load file or assembly &apos;CoCo, Version=2.1.0.0, Culture=neutral, PublicKeyToken=null&apos; or one of its dependencies. The system cannot find the file specified.&#x000D;&#x000A;File name: &apos;CoCo, Version=2.1.0.0, Culture=neutral, PublicKeyToken=null&apos;&#x000D;&#x000A;   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark&amp; stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)&#x000D;&#x000A;   at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark&amp; stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)&#x000D;&#x000A;   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark&amp; stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)&#x000D;&#x000A;   at System.Reflection.Assembly.Load(AssemblyName assemblyRef)&#x000D;&#x000A;   at Microsoft.VisualStudio.ExtensibilityHosting.FaultCatchingAssemblyLoader.&lt;&gt;c__DisplayClass17_0.&lt;LoadAssembly&gt;b__0(AssemblyName assemblyNameParam)&#x000D;&#x000A;   at Microsoft.VisualStudio.ExtensibilityHosting.Utilities.SafeGetOrAdd[TKey,TValue](IDictionary`2 dictionary, TKey key, Object lockObj, Func`2 valueFactory)&#x000D;&#x000A;   at Microsoft.VisualStudio.ExtensibilityHosting.FaultCatchingAssemblyLoader.LoadAssembly(AssemblyName assemblyName)&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.Reflection.ResolverExtensions.TryUseFastReflection(TypeRef typeRef, Module&amp; manifest)&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.Reflection.ResolverExtensions.Resolve(MethodRef methodRef)&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.Reflection.MethodRef.Resolve()&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.RuntimePartLifecycleTracker.CreateValue()&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.Create()&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.MoveNext(PartLifecycleState nextState)&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.MoveToState(PartLifecycleState requiredState)&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.ExportProvider.PartLifecycleTracker.GetValueReadyToExpose()&#x000D;&#x000A;   at Microsoft.VisualStudio.Composition.RuntimeExportProviderFactory.RuntimeExportProvider.&lt;&gt;c__DisplayClass15_0.&lt;GetExportedValueHelper&gt;b__0()&#x000D;&#x000A;&#x000D;&#x000A;WRN: Assembly binding logging is turned OFF.&#x000D;&#x000A;To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.&#x000D;&#x000A;Note: There is some performance penalty associated with assembly bind failure logging.&#x000D;&#x000A;To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].&#x000D;&#x000A;</description>
  </entry>

Currently classifications are not ordered in the CoCo/Classification page. Would be useful if the will be sort by alphabetical order.

all sayed ;-)
It would be a great shame if this great tool stopped working in VS 2022.

I recently move from Visual Studio 2017 to 2019 and when i set the Properties to bold, only the instance properties shows bold; the static properties are not affected.

The same problem with the rest of decorators but the colors and the rendering size works fine.

• Base tests for identifier declarations
• Base tests for identifier access
• Tests for identifiers in a xml comments
• Tests for vs14
• Tests for identifiers that are not reachable
• Tests for items classification in quick info

Need to add possibility to enable or disable classification in a xml doc markup

I understand not wanting to set colours by default but it's tricky to choose a colour scheme that works well. From your screen shots you have obviously spent some time doing this. Perhaps you might include a list of the values you have set for the various CoCo colour settings. We could still apply them manually bit would have your list as a guide. If your colour choices differ for the light and dark themes please supply a list of colours you chose for each.

Is it possible to share themes using CoCo, and if so, are you aware of any themes people have shared? (possible inclusion to readme)

Would be nice to add possibility to change font family for classifications

When using conditional code, i.e. #if DEBUG ... #else ... #endif the code highlighting does not correctly follow changes in the conditional state, such as switching between Release and Debug profiles.

In the attached image, the top screenshot shows some code in a file that was opened while the Release profile was selected and the lower shows how it changed when the profile was changed to Debug. The code in the #else should have become all grey but did not. When it was changed back to Release the display reverted to the top screenshot.

Versions are Visual Studio 2019 16.3.1 and CoCo 3.2.1

trying to get methods color'd yellow. Not all methods are working correctly, not sure if this is CoCo or something else. Both methods and extension methods are colored exactly the same.

I have attached my screenshot.

Installed on Visual Studio 2017 on Windows 7, where I was using the default dark theme. The installation immediately applied a light color scheme to the Text Editor only, and I cannot undo this. Additionally, as I can't uninstall the extension, I don't know if an uninstall will reset my colors.

To Reproduce:
Install Extension on VS2017 which is set to use default dark theme.

Destructor should be classified separately from any methods or should be classified as nothing

After the issue #3 was solved CoCo has a good way to introduce supporting of a new languages and the first of them should be Visual Basic, because roslyn supports it, so adding Visual Basic will be somewhat easier.

CoCo installed successfully as a non-admin user, however, uninstall as non-admin fails due to System.UnauthorizedAccessException. The specific registry key is \Software\Microsoft\VisualStudio[User_Dir]\ExtensionManager\PendingDeletions'.

To Reproduce:

1. Log into non-admin account in Windows 7.
2. Install package in Visual Studio from Extensions and Updates.
3. Restart Visual Studio and uninstall from Extensions and Updates.

So they can be styled differently.

Assume, that was introduce a new predefined classification type that broke classification of constant field as field.

It's should done before #17

Starting with preview 3 of the 15.7 version of VS 2017 the colorization is no longer working.
It worked as expected in preview 2, but then in preview 3 not longer working. Preview 4 was just released and it has the same problem.

For testing I installed a few other similar extensions and they too seemed to have the same issue.