External script editor not showing VScode as an option.

[LefySwefty]

I have had this same problem before where I’ve opened a script in unity and went onto VScode only to find that intellisense isn’t working. I ended up finding out that the fix for it was just going to external tools on Unity and changing the external script editor to VScode. But I have recently opened up a new project and had the same problem, so when I went to change back the external script editor I found that VScode was not an option. I selected browse and manually chose VScode. It shows up as Visual Studio Code (internal) (which is not what it showed up as before) and even after doing that I am still having the same problem. I have also noticed that the project files wont show up in the explorer panel in VScode, I’m guessing that this is the reason why intellisense isn’t working as I am not able to properly communicate with unity in the script. I have tried opening the project through VScode but this has also not worked. I noticed that when opening a script from another project, it would not only open that script, but it would also open the same VScode tab with the script from my other project on it, so this isn’t a problem with the individual project as I’ve also created more projects to test if it was still happening. I have checked my package manager, everything there is installed and up to date. I have tried deleting and reinstalling both unity and VScode to no avail. I have the .NET Framework 4.8 dev pack installed, my unity version is 2023.1.6f1, my VScode version is 1.80.2.
I’ve tried everything I could and haven’t found any answers.
I am very new so it is also much harder for me to wrap my head around all this.

[Kurt-Dekker]

VSCode isn’t support anymore, but here’s the Visual Studio links, plus a link to a third party support package for VSCode at the bottom:

This may help you with intellisense and possibly other Visual Studio integration problems:

Sometimes the fix is as simple as doing Assets → Open C# Project from Unity. Other times it requires more.

Other times it requires you also nuke the userprefs and .vsconfig and other crufty low-value high-hassle files that Visual Studio tends to slowly damage over time, then try the above trick.

Barring all that, move on to other ideas:

Intellisense Not Working with Visual Studio (Fix)

Likely, if you have appeared here to this page you are having the problem I had for the past hour or so. Intellisense is not working in Visual Studio. Well lucky for you, I figured out the solution to fix this issue after searching the entire web. So you don’t have to search the web anymore, I will tell you how I fixed the issue. Step 1: Close Visual Studio Step 2: In Unity, go to Edit < Preferences < External Tools (left part of the Window) Step 3: In External Tools go to the part that sa…

Also, try update the package inside of Unity: Window → Package Manager → Search for Visual Studio Editor → Press the Update button

Update: The VSC extension has been deprecated.

Update on the Visual Studio Code package

Hi everyone, We want to update you on the state of the Visual Studio Code for Unity package. This plugin was a result of one of our hackweek experiments by a few of our former employees. Unfortunately, it’s never been fully functional and hasn’t received any updates for almost two years, bringing you an unstable coding experience. We want to be open with you about its state so that you know what to expect. The scripting team has huge projects in the works with a significant impact for a major…

There is a community fork available that is receiving updates.

https://github.com/Chizaruu/com.tsk.ide.vscode

Also, this: No suggestions in Vscode