We read some settings from the devenv.exe.config file --- devenv.exe.config is not user mutable

We need an alternate mechanism to enable these features:

// App.config keys for determining whether not-shipping features are turned on or off
// Edit devenv.exe.config and place these at the end.
// <appSettings>
// <add key="fsharp-regions-enabled" value="true" />
// <add key="fsharp-navigationbar-enabled" value="true" />
// <add key="fsharp-standalone-file-intellisense-enabled" value="false" />
// </appSettings>

Because of this design the powertools who used this feature correctly, happened to cause VS update 1 to do bad things to people who use Dev 15 and the PowerTools.

[dsyme]

I think these features should be taken out of VFT (fully disabled and the code removed) and added to VFPT instead. They would end up much higher quality that way since they could be actively fixed. There’s no point having them in VFT as things currently stand.

[OmarTawfik]

As part of #913, these keys/opposite functionality would be removed, and we would depend on Roslyn’s infrastructure for that. Work is done on roslynbranch: https://github.com/Microsoft/visualfsharp/tree/roslyn