I have a MacBook Pro and and iMac, with the same version of Visual Studio Code installed on both. And on both I'm experiencing the same problem. Intellisense stops recognizing my user-made snippets at some point and I have to do a restart (which sometimes doesn't work).
I'm not using an extension for the snippets, but am manually entering them in preferences > user snippets, in the appropriate languages.
Anyone else have this problem?
Related
Maybe I am just missing something, but I don't get how to setup a blank solution in VSCode (Under Windows or Visual Studio, you are able to just create a new Blank NanoFramework Template, but how can I do that in VSCode :/). I would really like to work with the nanoframework instead of c/c++, but I don't know how to create a blank solution :(.
That option is not currently available.
The main goal of the VS Code extension is to allow (partially) folks on MAC or Linux to work with .NET nanoFramework.
It's not possible to debug on VS Code and you'll only have a full experience on Visual Studio. If you're on Windows, the recommendation is to use Visual Studio.
I'm developing an extension for Visual Studio Code for the proprietary language that the product I code for uses because I hate the antiquated IDE ships with it. Everything is going fine except for one issue. When I close and open Visual Studio Code, Visual Studio Code seems to "forget" my extension. Syntax highlighting, code completion, commands that I've implemented all stop working. I have to disable and then enable to extension for it to start working again. I am OK with this for personal use. However, I want to push this out to other users both in and outside of the company. If any code would be helpful, let me know, and I will happily provide it.
I resolved this issue. It was because in my settings.json for VS Code I had an entry for the file extension pointing to an extension that I had removed. Removing that line from my settings.json resolved the issue of things not working when I opened VS Code.
Thanks to everybody for their comments.
I do my editing for Xcode Swift source with Visual Studio on windows, which remotes into my Mac and Xcode.
When editing a .swift file, VS does pretty good, and correctly colors keywords.
But some commands don't work right:
comment and uncomment,
constantly pops up the [abc] help menu, which annoyingly obscures the source code,
new window command is not available.
I can't find a setting within Options > Text Editor to control this. And no StackO answers have helped.
Xcode does not support development on other devices than macOS.
Be happy that it works the way you describe it. Simply I would recommend to work on your Mac.
But if you want really to work on windows for native Swift development I would recommend to remote your Mac in a Windows window where you can use Xcode. Microsoft Instructions
Or instead of Visual Studio Pro try Visual Studio Code there are some free plugins which support the Swift Language. (e.g. Plugin: Swift Language)
I am developing Unity game apps on a PC using C#, using Visual Studio Code as the editor. The apps are targeted at PC and Android. Multiplayer uses Photon Pun 2.
The Unity version is 2019.3.14F1 - I don't want to move forward just yet in case of 'unexpected problems'.
The VS Code version was 1.48.3 - and everything was fine, no compile errors, all code working OK etc.
Stupidly, I took Microsoft's advice to update VSC, and VS Code went to 1.50.1. Result of this is that there are all sorts of errors showing up in VS Code relating to the Photon code. All these errors stem back to the 'using Photon.Pun;' line. It says "the type or namespace name 'Pun' does not exist in the namespace 'Photon' (are you missing an assembly reference?)".
The code however does not come up with any compile errors in the Unity editor itself, and it all runs fine, including the Photon parts. The problem is in VS Code.
I realise this is almost certainly as VS Code problem, not Photon, but I am wondering if anyone has met this before and knows how to fix it?
(This is why I do not want to move from 2019.3.14F1 to 2020.whatever at the moment - you never know what might happen).
I had the same problem. Installing different versions of VS Code / VS Community Edition didn't fix anything for me, but this did:
With the project open in VS Code, find all occurrences of
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
in *.csproj files, and replace them with
<ReferenceOutputAssembly>true</ReferenceOutputAssembly>
Tried rebuilding project files, swapping to a different editor (VS Community Edition 2019 - that was fine), but no difference - VSC persisted with the errors. Rest of intellisense working OK.
In the end, totally uninstalled VSC and reinstalled, and that sorted it out. No idea what the actual fault was.
I was wrong.
To-day, the errors are back.
The reason appears to be that in the process of trying to sort this, I installed VS Community Edition 2019 to see if that worked OK (it did). Then went back to VSC, and - that was fine too. Later I uninstalled VS Community Edition 2019 (it is taking about 4GB). It was uninstalling that which brought the errors back into VSC. Reinstalled VS Community Edition 2019, and it is all fine again.
So, VS Community Edition 2019 installs something that VSC needs - but I haven't yet figured out what it is.
UPDATE:
Gave up. Never managed to find out what VSC wanted and wasn't getting. Instead, reinstalled old version of VSC (1.48.2 from code.visualstudio.com/updates) and it is all fine again.
If still having this problem, all you have to do to fix it is by going to Package manager and install "visual studio editor package"
windows>Package Manager> All Packages /or Unity Registry (depeding on your unity version) search of visual studio editor
if it's already installed delete it and reinstall.
Got it FIXED!
Solution (it was a Unity issue):
In Unity, goto Edit > Preferences > External Tools > External Script Editor, and point it to Visual Studio..
Why this was so hard to find, I have no idea. But now my Photon solutions and namespaces properly transfer from Unity to Visual Studio. Hooah!
Also moved the script to where the photon scripts are
Uninstall the Visual studio community and re-install with latest VSC 2022. It will fix the issue
When I start Visual Studio Code (Win10[64bit]), click on extensions overview, all my extensions disappeared. The overview is empty. I also can't load any new ones. But I think all the extensions seem to work.
In Addition there is a clock on the extensions symbol and it seems "loading", but nothing happens. Waiting a long time or restart didn't improve anything.
This is my first question, thanks for help.
As commented by the OP above:
Thanks for your ideas, I re-installed and everything is fine now.
The hint came from Maja Okholm:
perhaps try to repair the installation of visual studio code? Control panel > programs > programs and features, find visual studio code and click repair