6 Commits

Author	SHA1	Message	Date
Connor Peet	c536595a7f	cli: fallback to system installs in the standalone CLI ... The standalone CLI should detect and fall back to using and system-installed VS Code instance, rather than trying to download zips and manage its own VS Code instances. There are three approaches used for discovery: - On Windows, we can easily and quickly read the register to find installed versions based on their app ID. - On macOS, we initially look in `/Applications` and fall back to the slow `system_profiler` command to list app .app's if that fails. - On Linux, we just look in the PATH. I believe all Linux installers (snap, dep, rpm) automatically add VS Code to the user's PATH. Failing this, the user can also manually specify their installation dir, using the command `code version use stable --install-dir /path/to/vscode`. Fixes #164159	2022-10-20 10:54:13 -07:00
Connor Peet	7c3740a7e7	update prepare scripts, license, lockfile	2022-10-17 11:50:49 -07:00
Connor Peet	450f8e65b6	run cli tests on pr	2022-10-17 09:56:15 -07:00
Connor Peet	a2dd71c0fe	cli: use openssl for all crypto-related activities ... For compliance with SDL and MSFT crypto standards. Right now this uses our forks of russh and secret-service. russh seems amenable to getting this merged (https://github.com/warp-tech/russh/pull/52) but TBD about the secret-service crate. Fixes https://github.com/microsoft/vscode-internalbacklog/issues/3158	2022-10-14 11:09:31 -07:00
Connor Peet	5b24e93b35	cli: update problematic dependencies	2022-09-20 08:57:55 -07:00
Connor Peet	3762635fe1	move cli to top level	2022-09-20 08:42:44 -07:00