I’m trying to update a project from 2021.3 to 2022.3, and it seems the solution was mangled (many packages can’t be found) so I want to regenerate the solution, and usually I do this with the option in External Tools (as per Unity - Manual: Preferences).
Problem : I don’t have the option anymore.
I checked that I have the Visual Studio Editor Package, and tried using many different exe ad an IDE (see screenshot, the default should be Rider as that’s what my team uses).
I’ve uninstalled and reinstalled Unity 2022.3, which didn’t change anything.
Note : all the IDE options are below the break and show as (internal), whereas they were “normal” in 2021.3. I don’t know what that means or how to make them show as recognized.
External Tools don’t show the opition no matter what IDE is selected
Unity 2022 really isn’t ready for LTS. It has a TON of outstanding issues. I see at least a half dozen posts in here every day it seems, such as the “can’t edit existing animation keys” post just an hour ago.
Either way, Assets → Generate C# project is your go to option.
And here’s the general intellisense blurb… good luck in 2022!!
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.
Also, try update the package inside of Unity: Window → Package Manager → Search for Visual Studio Editor → Press the Update button
Depending on flavor and version of Visual Studio, it may also have an installation step that you perform within the actual Visual Studio. This step seems finicky at best and may require multiple openings of VS before it comes up.
Update: The VSCode extension has been deprecated and abandoned:
Note that you do not need this option. Simply deleting all .csproj and .sln files in the project root, then double click on any .cs file in the editor will regenerate the sln and csproj.
What exact version of 2022.3 are you using?
Did you try creating a new project with that version? If so, if it looks the same I would assume a bug or an issue with your system, oherwise it‘s an issue with the project. Since you use Rider try removing both Visual Studio (Code) Editor packages.
Hi al and thanks for your answers.
The exact version is 2022.3.7f1. It’s a fresh install That I’m trying to test some newer API that seemingly didn’t exist in 2021.3 (although it seems to depend on how I navigate docs.unity3d.com. I really wish the site documented the version introducing a method).
A new project works normally, and I noticed that the IDE options are correctly labelled, and displayed above the fold as seen in this screenshot. Notice it says Rider 2023.1.4 as opposed to Jetbrains rider (internal). I can’t find any docs as to what displays these and why they would be incorrect.
I’m reverting to 2021.3 as I’ve already lost 2 days to this. It certainly has been a… sobering experience.
I’ve had issues with the IDE dropdown myself before, where Rider was missing. You can always use Browse and point to the actual exe, that worked for me.
Part of this may have been due to a broken layout I had imported. Try “reset all layouts”.
Otherwise try uninstalling all IDE packages and re-install only the one you intend to use, ie Rider.
In Unity600.0.27f1 (latest I have here) you can regen project files in one of two ways, starting from the main menu:
Assets → Open C# Project
OR
Edit → Preferences → External Tools
In the latter is also a bunch of checkboxes for WHAT to generate.
As a third method, you can delete ALL the .csproj and .sln files first, then you can even doubleclick on a C# file and it should regen as well.
Meanwhile, here’s more notes:
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:
Also, try update the package inside of Unity: Window → Package Manager → Search for Visual Studio Editor → Press the Update button
Depending on flavor and version of Visual Studio, it may also have an installation step that you perform within the actual Visual Studio. This step seems finicky at best and may require multiple openings of VS before it comes up.
Update: The VSCode extension has been deprecated and abandoned:
Update: the VSCode integration is back… maybe!?
There may be a community fork available that is receiving updates.
Recently (July 2023) I worked on a Windows11 system that required a Microsoft component to be installed from within Visual Studio before it would work properly with all the OTHER software installed under Unity. I have no documentation on that process as I have only seen it once and it surprised me as well.
