Is there an easy way to uninstall the FTP-Sync package I have installed in VSC? There doesn't seem to be a remove feature
You can see all installed extensions and uninstall them using these steps:
Ctrl+P(Quick Open).
Enter >Extensions: Show Installed Extensions.
Click the "x" icon next to the extension you want to uninstall.
Here is how is looks:
Related
Today I tried to use the copilot, but suddenly this error start appearing:
[INFO] [fetch] [2022-05-19T21:00:55.452Z] Please upgrade your Copilot extension to continue using this service.
I tried to uninstall and install again and reload, but nothing happens, anyone have any idea how to solve this problem?
There's an error description in the image below:
This can be resolved by upgrading VSCode itself: Help → Check for Updates / Install Available Updates.
You may or may not need to re-install the extension and re-authenticate with git.
Reference: https://github.com/github/feedback/discussions/15684
In my case (on a mac) I had to do the following:
Move Visual Studio Code from Downloads to Applications
Restart
Update Visual Studio Code
Sign into Github
Open extensions and locate Github CoPilot
Click "Reload Required"
As #emragins suggested, go to Help and check for updates/restart to update
Once you are back on VS Code check if the Co-pilot is activated.
If it is not activated/still gives the same error.
Search for co-pilot in VS Code extensions search
Click on co-pilot extension in the search results, you should see restart/reload required.
Reload and it should be working now. If not try closing VS Code and opening it now.
You should uninstall the extension and download the latest version from this page in the form of VSIX file. After that you can install the extension from that VSIX file.
I think it is because there is some API changes and the latest version of the extension. However, it is still marked as preview. When we click on install from the built-in extension browser, it just install the latest stable version.
https://marketplace.visualstudio.com/items?itemName=GitHub.copilot
if you are on a linux device, update your vscode first then update your co pilot extension it will work.
In vscode extension marketplace , I am getting the option of powershell preview version and not the stable version. Is there any other alternate to solve this issue?
In VS Code:
Open Extensions
Select PowerShell extension
Click the Manage cog-wheel (bottom-right corner)
Click Install Another Version... from the menu
Choose a version you feel comfortable with.
Note: I highly recommend running VS Code elevated (run as Administrator) to ensure installation of new extensions run smoothly.
Hope this helps.
These days, anytime I start VSCode, I get this warning
You are running the system-wide installation of Code, while having the user-wide distribution installed as well. Make sure you're running the Code version you expect.
Please how do I fix that?
UPDATE (Recommended by #Fabio Turati)
Just uninstalling the older one without the (USER) extension, it seems working. If not, then uninstall the one left and reinstall vscode.
additional reading:
You installed the new one (with USER extension) before uninstalling the older one. So now you have both, and this is why you get that message. You need to uninstall them both, then reinstall vs code. Make sure you add a shortcut on desktop, it took me a few more minutes to find the .exe of vs code. No worries you don't lose anything by uninstalling...
cheers !
You probably have both versions installed (like I do).
To get rid of the warning, make sure you open the user-wide version. That means unpinning the one you used to have from everywhere.
Then use windows (10) search: visual studio code . Only the ' user-wide distribution' gets shown. If you open visual studio code that way, the warning is gone.
i had these installed:
uninstalled the first one and that error message is gone.
The new executable of the "user-wide distribution" is in this location by default:
C:\Users\<username>\AppData\Local\Programs\Microsoft VS Code\Code.exe
Replacing your shortcuts with this one should make sure you are using the new installation. (You can also uninstall the old one of course if you want to)
Run into this issue today but all I did was install the new one one (with user extension) and then after successful installation I uninstalled the the old one. Restart my computer and all seems to be ok.
I magically solved by (using windows 10):
Unpin from "taskbar" the vs code shortcut
Remove the shortcut from desktop also if you have it
Search on cortana "visual studio code", once the app appears right click and select "pin to taskbar"
Open tha vs code app from taskbar and the error should be gone.
When I try to install any extension in Visual Studio Code (i.e., by pressing Ctrl+P and then running ext install RustyCode), I get a message that No extensions found.
However, this only happens when I run VS Code directly from source repository. I.e., after:
git clone https://github.com/Microsoft/vscode.git
cd vscode
git checkout 1.0.0
scripts/code.sh
But, if I run VS Code from official builds, then I'm able to install extensions.
So, how can I enable downloading and installing extensions from Visual Studio Marketplace when I run VS Code directly from source repository? (Is Visual Studio Marketplace integration bundled separately in official builds?)
I'm on Ubuntu/Linux.
This can be fixed by adding following to product.json:
"extensionsGallery": {
"serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
"cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
"itemUrl": "https://marketplace.visualstudio.com/items"
}
(This is can also be fixed by copying product.json from an official build (in the .zip archvie, product.json is under resources/app) which contains above lines).
More information: https://github.com/Microsoft/vscode/issues/1557
You can use code-marketplace extension in AUR to add microsoft marketplace registery in code OSS. This extension will installs a pacman hook that patches the file on every package update.
If you want to do the same for archlinux, have a look here => https://wiki.archlinux.org/index.php/Visual_Studio_Code , you have various possible options to solve the problem.
For Arch linux you could access the product.json file under this path - /usr/lib/code/product.json.
Just edit on the file the extensionsGallery with the following-
"extensionsGallery": {
"serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
"cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
"itemUrl": "https://marketplace.visualstudio.com/items"
}
like #Vikrant Chaudhary said.
Extending the answer from #Vikrant Chaudhary. If anyone wanted to do the same thing on Windows, the path to product.json is here:
Windows path for VSCodium: C:\Program Files\VSCodium\resources\app\product.json
I start using vscode less than a month. Please forgive me if this is a dump question.
OS: OS X 10.11.3
VSCode: 0.10.6
Plugin: VSCode-PHP-Format (download via git clone)
Extension path: ~/.vscode/extensions/VSCode-PHP-Format
I restarted VSCode, open php files, but do not see "Format Code" on the right click menu.
Any idea how to debug this? Right now I don't even know if the plugin load correctly.
With tips from Tobiah Zarlez, I found the "Toggle Developer Tools" in VSCode.
It is shown in the console the plugin cannot find js-beautify.
Solution
Inside ~/.vscode/extensions/VSCode-PHP-Format, run
npm install
It will pull in js-beautify. Then restart VSCode.
I am on my phone and not able to double check to see if it is there, but I'd recommend installing from the visual studio marketplace to insure the plug in is installed correctly. You can do so by hitting CTRL+SHIFT+P and typing "install extension"
Beyond that, a quick glance at the code the plug in should be activated when you open a php file... but since this is a third party plugin, I can't speak to if it actually works or not.
(Again, on phone so can't test)
What you could do is modify the extension.js file to add a "console.log ("hello world")" to the activate function. Them check the log to see if the plug in is installed correctly.
I saw you weren't the only person to complain about the plug in not working though. If I were you, I would continue to try and contact the creator