@WrongBit I've added support for styling: https://vlasovstudio.com/task-canvas/TaskCanvas_260.vsix
You can now set for example the following style in Task Canvas options to make the file name bold in a fragment title:
<Style TargetType="TaskCanvas:TabFileName" BasedOn="{StaticResource DefaultTabFileNameStyle}">
<Setter Property="FontWeight" Value="Bold"/>
</Style>
@MrClyfar Yes, I can reproduce this problem.
It looks like NCrunch doesn't support advanced Visual Studio editing features that Task Canvas leverages. For example, even without Task Canvas, if you open Window – New Window for Calculator.cs, in the second Calculator.cs:2 window the code coverage symbols will not be displayed.
I've noticed that when I have VS2019 configured to restrict formatting to "changed lines", ContinuousFormatting doesn't seem to follow that restriction, and changes otherwise-untouched lines in code (even when VS2019's settings are to leave spacing as-is in those cases). In team environments, that can be problematic, filling up commits with format-only changes (particularly undesirable in maintenance repos).
It's definitely CF plugin causing the (mis)behavior, because the behavior ends when CF is disabled/uninstalled, and returns when enabled/reinstalled. If VS's format rules say to leave a given situation as-is for spacing/alignment/breaks, I do not understand why ContinuousFormatting causes formatting to change untouched lines.
This can become a real problem, esp. when VS's native formatting controls don't quite support the team or project format standards -- normally the answer is just to leave the "atypically-formatted" lines untouched, or manually fix them, but with ContinuousFormatting that means having to remember to disable the plugin before working on such projects. I'm open to any suggestions on how to get CF to change this behavior?