Update (2018-09-18): I had this wrong. I was able to disable the Live Share and Azure extensions in VS Code. I just wasn’t paying close enough attention to the error messages I highlighted below.
You can disable the both the Azure and Live Share extensions by first disabling their dependencies. In the case of Live Share, I first had to disable the Live Share Audio extension. In the case of the Azure extension, I had to disable the Azure Functions extension first.
I like VS Code. That, in itself, still surprises me a little given which company created it. I still remember the Old Days when Microsoft took every opportunity to coerce users to use its solutions, often using pretty aggressive tactics.
Many have said that we’re dealing with a new Microsoft, friend to the FOSS community, trusted custodian of critical platforms like GitHub. That may well be true. At the same time, I still see a little of the old Microsoft seeping through now and then.
I opened VS Code today, to take a look at some code I’ve been meaning to continue working on. I noticed that Live Share updated when I open the app, and then seemed to start running for some reason.
I don’t use Live Share (although the functionality is interesting).
Rather than have extensions running that I don’t use, I thought I’d disable Live Share, along with the Azure extensions that seem to be installed and activated by default. That didn’t quite work out for me.
As good as VS Code is, I don’t like being required to keep Microsoft’s extensions installed when I don’t make use of them. I’d expect that from an application that doesn’t hold itself out as “extensible and customizable”.
This just taints the progress the company has made, to a degree. It also leaves me wondering what else is running in VS Code when I use it, that I didn’t enable?