Plugin disable itself for no apparent reason

[mastoj]

Description

The plugin gets disabled for no reason. So I don't get any of the help from FSharp Power Tools.

Repro steps

Don't know how to repro since I haven't seen this on any other machine. I could provide some logs if that is possible and you guide me.

Expected behavior

It shouldn't be disabled for no apparent reason.

Actual behavior

It should stay enabled.

Known workarounds

Enable it again and restart VS.

Related information

• Operating system: Windows 10
• Extension version (e.g. 2.3.0): 2.5.0 (was also present in 2.4.1)
• Visual Studio version (include Updates 1, 2, etc.): Enterprise 2015, Update 2
• Other extensions installed in Visual Studio: Resharper,

[masq6r]

I have such issue as well... Writing the code and all of a sudden the extension is disabled and the syntax highlighting works no more.

[cloudRoutine]

I noticed the extension was disabled after I installed resharper. Several other extensions were disabled as well. I suspect resharper is the cause.

[masq6r]

I noticed the extension was disabled after I installed resharper. Several other extensions were disabled as well. I suspect resharper is the cause.

I really doubt because I don't have Resharper installed.

[dungpa]

@codefour @mastoj Could you try the workaround described at VsVim/VsVim#1804 (comment)? It seems like a bug of Visual Studio itself.

[masq6r]

@dungpa Thanks for your response. Your quoted workaround fixes the issue, so far.

[JanWosnitza]

Reinstalling the plugin fixed it for me (at least for the moment ^^).

PS: The plugin still worked with some solutions but suddenly disabled itself on other solutions. Didn't recognize a pattern.

[idg10]

After about 10 attempts to uninstall the extension failed, I ran this from the command line:

vsixinstaller /u:FSharpVSPowerTools.68b42cfe-c752-4094-8dba-ed48aa81cac8

That finally got rid of it, after which I was able to re-install, and it started working again.

[idg10]

...but it still regularly disables itself. I've been running with the F# Power Tools content in the Output pane showing in the hope of catching the problem. But I'm now fairly sure that what actually happens is that it gets set into a state where VS thinks it's disabled, and so if you quit and restart VS, it's no longer available. So there doesn't seem to be an error message to report.

[cloudRoutine]

This has been happening to me as well, but in the larger context of vs2017 and vs2015 disabling each other's settings, often while both are running at the same time and I have no idea what to do about it.