VS has gotten really bloated with creating extra processes when all I do is start it up or load a solution. It is getting a little out of hand. I notice that when I start VS with Live Share installed it creates a vsls-agent process. It doesn't matter whether I ever actually use the extension (which I rarely do when not working remotely). Yet this process is running in the background.
Please don't start the vsls-agent process until I do something with the extension that would trigger it's need such as trying to start or join a session.
Adding @Chuxel, @lostintangent, and @jonwchu.
@CoolDadTx try to modify the package.json file in the root directory of the extension, they are located in %USERPROFILE%.vscodeextensions in Windows find the extension folder and try to play with "Activation Events", it's not recommended method so create a backup of the package.json!
@tsvetilian-ty , sorry I should have clarified. This is for VS 2017, not VS COde
@lostintangent @srivatsn Launching the VSLS agent process at startup helps us to shorten the time taken by the first share workspace operation. I think it'd be reasonable to make it configurable and let the user decide whether they need this aggressive optimization.
I would like to see this made configurable as well. I use live-share frequently enough that I want to keep it installed all the time, but so infrequently that I'm willing to pay the startup time cost on the occasions that I do want to use it.
Most helpful comment
@lostintangent @srivatsn Launching the VSLS agent process at startup helps us to shorten the time taken by the first share workspace operation. I think it'd be reasonable to make it configurable and let the user decide whether they need this aggressive optimization.