My fresh install of Unity 2022.3.2f1 and Visual Studio 2019 did not automatically install the “Visual Studio Editor” package into Unity. I have been searching high and low to try and find some sort of way to add the “Visual Studio Editor” to my Unity package manager. Can anybody provide me with some sort of git URL, package name, exe, “tarball”, zip file, thumbdrive, floppy drive, hard drive or cassette tape that will allow me to click the little plus symbol in the package manager, select the “Visual Studio Editor for unity.exe” file and install it on my version of Unity.
Even Microsoft’s own website lacks the instructions to install this package. They have a section entitle “Install or update the Visual Studio Editor package” where they go on to to tell you how to update the package, making no mention of how to install it.
I am sure this question has been asked a million and one times, and yes I have searched the forums. However, searching “add Visual studio editor” yields zero relevant results within 27 pages. And I have of course searched google for many variations of “Add visual studio editor to unity packaged manager” to no avail.
Is it not listed in Package Manager when you switch to „Unity Registry“ in the top left corner of the package manager window? That‘s where you‘ll normally find it.
THAT is where it is located! Thank you! If only one of the 3000 videos I watched on how to get Unity and Visual Studio to talk to each other brought this up, I would be set.
Sadly, adding the visual studio package to Unity still has not made Unity and Visual Studio want to talk…
I still get the dreaded “Miscellaneous Files” instead of the Chad “Assembly-CSharp”.
I supposed it’s understandable. I mean computer programming only came out like 100 years ago, I wouldn’t expect them to have the finer details ironed out quite yet.
Update: Okay, there is, misunderstood you. Can’t comment on this though other than using a 3-year old VS with latest Unity could be problematic from past experience, but so was my entire VS experience.
I know right? Every step of the way with Unity has been an uphill battle. The program seems like a dam made with subpart cement, and all the devs are just running around with bubble gum trying to plug the leaks.
It’s probably time to say goodbye and embrace the CCP powered Unreal.
No no no. I was talking about Visual Studio! They don‘t nearly support Unity well enough as they could - it‘s just that Microsoft has Visual Studio customers relying more heavily on anything but Unity. That‘s a market gap JetBrains jumped in with Rider. Give it a try, you‘ll see almost all of the issues are because of Visual Studio integration with Unity, and you‘ll finally get rid of „uncalled method: Update()“ and such nonsense.
Looks perfect. So much better than VS. If I ever decide to elevate my investment into Unity beyond $0, I will def do it with Rider.
By the way, I solved my problem. Turns out the project file was the culprit. I made the mistake of already having VS installed, not letting Unity install it. so when I created my project file, it created some freak of nature project file that VS and Unity did NOT work together to create.
So in the end, I threw the baby out with the bathwater and started a new project with the newly married VS and Unity.
And like the Phoenix rising from the ashes, this project file flies further, higher and faster than before. It also gives me intellisense.
All should go well, until I decide to commit the ultimate sin of moving my project file to another computer.
Oh, this is still an issue after more than 5 years?
In that case, if it ever occurs again or something similar (no Intellisense etc) then just delete the .csproj and .sln files from the project folder (close VS before doing so).
