A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate
in the Unity community.
Separate names with a comma.
Discussion in 'Code Editors & IDEs' started by DavidG_Fenex, Feb 27, 2020.
Thanks Man it worked!!!
nothing else worked but this worked thanks alot!!!!
I wonder why is there visual studio code editor and then visual studio editor, why have both if the first one works just fine and the latter causes bugs?
Thanks Man, It worked perfectly.
I've done all but check if the editor attaching is ticked. However, I can't find an option for editor attaching?
I saw that it is displayed in the docs (below), though I can't seem to get it to appear on mine.
I think we have to press regenerate files afterwards too.
Thank you soo much, it fixed all the errors
That totally works for me. Manyyyyy thanks
God bless you and your family!!
Thank you, very much! Appreciate it!
THANKS SO MUCH!
Thanks, it worked!
None of this stuff is working for me.
Visual Studio Community 2017 15.9.14
-ensuring all Unity packages (including visual studio editor) are up to date
-deleting Library and letting it re-import everything
-deleting all csproj files and then checking all boxes and re-generating the files.
I still get this result:
The strange thing about this was that it was only happening in a single project on my computer. All other projects using that version of Visual Studio Community 2017 were working fine, even when I opened the same script as in the screenshot.
I updated to Visual Studio Community 2019 and the issue went away. I'm really not sure why that was necessary since 2017 was working fine with Unity 2020.3.20f1 on all other projects on my machine.
I fix the issue by repairing Visual Studio using 'Visual Studio Installer'
This worked for me. Unity 2020.3.20f1 Personal.
With Visual Studio 2019 Community.
Thanks a lot, it worked for me, too.
I bit the bullet and downloaded the full Visual Studio for Mac. I gave up on Visual Studio Code after a few hours of going in frustrating circles and trying several suggestions on the Unity forum and StackOverflow that didn't work.
One thing I noticed right off the bat is that the Visual Studio installation will automatically prompt you to download the necessary .NET stuff. I didn't have to run any commands to install things once Visual Studio was installed (although, I did download the dotnet and Mono installations previously for VS Code, so who knows if these were used or not...).
Once Visual Studio for Mac is installed, I went into Unity and gave Visual Studio Code the ol' boot by updating my preferences to open Visual Studio as my external editor:
Unity version: 2020.3
Unity > Preferences > External Tools > External Script Editor > Visual Studio for Mac [8.10.11]
I've also got Package Manager > Visual Studio Editor installed (2.0.11)
Finally, I opened my .cs file from within Unity (alternatively, you can right-click and select Open C# Project). Once Visual Studio opened:
Visual Studio > Preferences > Theme > Dark (we aren't barbarians...)
...and then File > Open > and opened my Unity game .sln file.
I went to the script in question to try things out and badda-bing-badda-boom, intellisense and all my stuff worked and opened without a hitch.
Best of luck.
Post of the year! THX a lot!
Thanks a lot, it helped!
This awful bug has driven me crazy for about 3 days now.
So, thank you man, your solution was the best thing that has happened to me in weeks!
Absolute Legend it worked
I tried basically anything that I saw resolved the issue for anyone else while I was researching. After a whole day of troubleshooting this the only thing that fixed it was going into the root folder of the project within file explorer and then on the .csproj files I changed the application type for opening that file type to VS Code. Additionally it seems I am only able to open a fully functional window of VS Code without opening it through Unity. When I open the project directory folder directly with VS Code and then launch my Unity project everything seems to function as it should
Not sure if this will help anyone else but I wanted to throw it out there since I had such a hard time solving it myself.
You saved my life!!!
That's what worked for me, all of the above did nothing (in VS Code). And I think I found this out befoe and forgot about it...like you! Thanks for putting up the reminder for me.
tyhank you so much i love you man
Worked for me:
Closed Visual Studio
Opened Preferences in Unity Editor
Click External Tools (Left hand menu)
Change External Script Editor to: Visual Studio .... (Shows the full name)
Clicked on the "Regenerate project files" button.
Closed project/re-opened, double-clicked a script, Visual Studio launched and Intellisense is back!
Thanks, that worked!
It worked for me. thanks a lot.
@RowdyCoder I'm working on Unity 2020.3.25f1, and nothing was working. I did what you did and it worked! thank you
Thanks for the quick solution
THANKS SO MUCH IT WORKED
That's awesome! It works like it should
Thank you! worked for me as well!
It works ! Thank you!
this somehow worked on 2020.3.28, thanks!
After some hours lost in getting this thing done and nothing work to me I decided to look omnisharp log and it clearly states:
Look the f installation page for mono. BUT READ IT ALL!!!!
https://www.mono-project.com/download/stable/#download-lin-fedora (i use fedora, but choose whatever you have)
dnf install mono-devel
The package mono-devel should be installed to compile code.
The package mono-complete should be installed to install everything - this should cover most cases of "assembly not found" errors.
The package referenceassemblies-pcl should be installed for PCL compilation support - this will resolve most cases of "Framework not installed: .NETPortable" errors during software compilation.
The package xsp should be installed for running ASP.NET applications.
YES! Install mono-devel, mono-complete referenceassemblies-pcl AND xsp!
close VSCODE and reopen it from inside Unity.
you now have beautiful GET COMPONETE in your intellisense. FUUUUUUUUUUUUUUUu took me 2 hours!
thank you so much!
Thank you so much! It even works with VS 2022 and Unity 2020.3.22.
thank you so much
Thank you so much! Perfect solution! I have been losing my mind for days trying to figure this out.
Thank you so much bro.
I can't express my thank you. "Regenerate project files" in Preferences>External Tools fixed it. Finally I can get on with this project.
I tried everything to make this work with Visual Studio Community 2019. Uninstalled and reinstalled. Tried all the suggestions in the thread and nothing worked. I prefer VS Community 2019 since that's what I've used for a long time.
What ended up working for me is installing Visual Studio Code, and switching to that editor for my project. Still not thrilled, but using a less preferred editor w/ intellisense is better than none at all I suppose.
(Edit): Although, the intellisense still does not perform like it does for users in the tutorials I watch. I don't get suggestions until I've typed a complete method or property. It will then just load a list of what already exists in the file. Guess I'll just have to remember everything. lol
Thankkkk you sooooooo muchhhhhhhh IT HELPED A LOT!
Top banana, big thanks...! other places have said update and reinstall, nothing worked apart from this! I couldn't find 'Editor Attaching' but obviously not a problem for me!
Does anyone know how to get IntelliSense working for Shader files in Visual Studio Mac? I've never had an issue with IntelliSense in my C# files and it works perfectly, but I get nothing for .shader files. The MS Docs say that shaders are supported, but when I try the steps in the original post, i.e. enabling everything in External Tools and "Regenerate Project Files", it doesn't do anything..
I'm new to Shaders so not having IntelliSense makes things extremely difficult. Please can somebody help?
Intellisense is constantly breaking for me (Unity 2019, VS Community 2019) and the debug drop changes. It might be when I switch to a 2020 project and back, I don't know, but I have to hit "Regenerate project files" every time it happens - to fix. Annoying!
Also the Regenerate button is hidden away in preferences? Right now it is a regularly needed thing so it should be in a menu, not hidden away!
Is this an MS bug, a Unity bug, where does the issue lie & when will it be fixed?