Intellisense Not Working with Visual Studio (Fix)

Still working - thx.

 

What a joke
2019.4.23 LTS version not work with Mac Visual Studio, it should be a stable version
Double click on console does not take me to the line, what a painful for debugging

Mac OS Big Sur 11.23
Unity 2019.4.23 LTS
Visual Studio for Mac 2019 Community 8.9.5 (Build 5)

Unity -> Preferences -> External Script Editor -> Select as Visual Studio
Generate .csproj files for: All checked and clicked Regenerate project files then restart Unity
Visual Studio make sure it is "Attached to Unity"
Package Manager -> Visual Studio Code Editor -> Updated to Version 1.2.3 (2019.4 verified)
Tried downgrade also not work.

 

What he said. Debugging and Intellisense were back after doing this.

 

OH GOD! THANKS! It's working!
(Unity 2021.1.2f1 & VS2019 16.9.4)

 

If you are still having this problem

See if this helps:

1) Go to Visual Studio Installer (link below if you need to download it again)
https://visualstudio.microsoft.com/downloads/

2) Choose 'Modify' button on your installed version of VS



3) Enable Game development with Unity

 

It worked for me, thanks, DavidG_Fenex!

 

Here a solution, go to folder game, enter on "yourgame.sln" ,vstudio will open by default.
Then go to unity and select enter script you do want open , buala!
inteligence will work, i dont know why , i did open script from unity editor dont work.

Recapitulate:
-Open file/ project.sln
-On unity editor/ open script.
this should working.

good programing.

 

Hey everyone, I think I found a solution! (Unity 2019.4.23, Visual Studio Community for mac v.8.9.7 build 8)

- Open solution in VisualStudio (double click any script in unity project)
- Go to View -> Solution
- From the solution window, select all .csproj files (at this point they name should have (unavailable) postfix)
- Right click on them, and choose reload.
- Restart Visual Studio if needed

Did it work? Let me know!

P.S. @John_MSFT just wanted to tag and let you know about this solution, since you're PM on the microsoft team

 

thank you

 

You're a hero.
Thanks to you, I solved it. Thank you.

 

Worked like a charm! Thanks so much!

 

This literally made my day. Thank you so much!

 

It works, thanks

 

Dude it seems like im too dumb for this... can you maybe add me in discord and watch me trying to fix it and tell me what to do... altough this seems weird im just F***ed up at this point
Add me if you want to: SpaceNoob#5961

 

This is correct.

 

Step 3:
In External Tools go to the part that says External Script Editor (this should be on which ever Visual Studio editor you are using (for me it defaulted to "Open by File Extension"

This fails to save when I close Unity 2020.2.1f1
So when I reopen Unity I have to all the steps over again.

Anyone have a fix for this?

 

I have both VS17 and VS19 on my system as I was upgrading. Working fine with VS17 forever but the new VS19 does not have Intellisense. In Unity 2020.3.9 I changed "External Script Editor Args" from the default "open by file extension", to the specific version of VS19 that I want to run. Open a script in Unity and once VSxx opens, wait 10-15 seconds. The intelisense becomes highlighted as expected.

FYI: I will be going back to VS17 because it doesn't have the 10-15 second delay. Don't know what that is about.

 

Updating from 2020.3.8f1 to 2020.3.9f1 still had the issue that visual studio didn't find the unity packages. Closing VS and regenerating the project files before loading it again solved the issue.

 

it worked perfectly, thank you very much for your good work

 

Thank you!

 

Thanks, it worked!

 

Thanks for this. It works for me.

 

Thank you, This was a quick fix to an annoying problem.

 

this fixed my issue as soon as I told it to use "Visual Studio community 2019" instead of "open by file extension"

 

I was having this issue on macOS and, after following a whole chain of fixes from this thread, I got to the point where I received the following error message every time I opened the script in VS Code:

"Some projects have trouble loading. Please review the output for more detail”

To resolve this I needed to:

• Download the latest version of Mono
• Go into Preferences > Settings and search for "OmniSharp"
• In "OmniSharp: Path" go into "Edit settings in.json" and add: "omnisharp.path": "latest"
• Set "OmniSharp: Use Global Mono" to always

Then it miraculously worked.

This. took. me. forever. To figure out. Hopefully it helps someone else save some time!

 

Thank you, this worked perfectly, but I had to select Visual Studio Community in the 'external script editor' drop down before it gave me an option to generate .csproj files. It didn't show me the option to generate .csproj files when it was set to 'open by file extension'

 

Visual Studio for Mac is a bit weird to me, from switching to a Windows to a Mac. I was confused why there was no option to download any modules like Unity, Python, etc. It seems like VS for Mac has Unity Intellisense built-in, all I had to is update the intelligence through the package manager.

 

For anyone this may help and apologies if this was mentioned and I missed it- I tried everything listed in this thread and still couldn't get Intellisense working. I tried clicking the button in Visual Studio that says "Attach to Unity" and then hit the little red stop button. Intellisense then worked perfectly.

 

This works for me but now build for android takes a lot, like 16min.

 

Thank you very much!!!
This solved the autocomplete issue and the syntax coloring!

Wish you all the best!

Regards,
Mitko

 

Thank you!!

 

It worked perfectly.
Thank you very much!

 

All I can say is thank you for saving me browsing all the web.

 

Worked in 2020.3.12f1 perfectly as well

 

LifeSaver! I bookmarked this for next time if I forget.

 

Unity 2019.4.19f1 with Visual Studio Community 2019 version 16.10.4 with Windows 10 fully updated.

No Unity intellisense, it doesn't highlight even the classes I created, before this project I was using Unity 2017 and it was slightly less weird, but sill...

I am trying everything I find on the internet.

 

Updated VS then encountered "Visual Studio Can't Find Monobehavior". Needless to say, Intellisense wasn't working either. Unlike the OP (DavidG_Fenex) I switched External Script Editor to Open By File Extension, then double-clicked a script. The problem was already solved. Weird. I went on to follow OP's steps just to be sure. Everything is still groovy. Thanks David!
VS update 2019 16.10.4, Unity 2020.3.14f1.

 

It worked perfectly, thank you!

 

THANK YOU SO MUCH BRO I AM SO HAPPY THANK YOU SO MUCH IM 11 AND IM TRYING TO MAKE GAMES FOR FUN TYSM!!!!!!!!!!

 

[QUOTE = "DavidG_Fenex, post: 5527864, membro: 4514596"] Provavelmente, se você apareceu aqui nesta página, você está tendo o problema que tive na última hora ou assim. O Intellisense não está funcionando no Visual Studio. Para sua sorte, descobri a solução para corrigir esse problema depois de pesquisar em toda a web. Para que você não precise mais pesquisar na web, contarei como resolvi o problema.


Passo 1:
Fechar Visual Studio

Passo 2:
No Unity, vá para Editar <Preferências <Ferramentas Externas (parte esquerda da janela)

Etapa 3:
Em Ferramentas Externas, vá para a parte que diz Editor de Script Externo (deve ser em qualquer editor do Visual Studio que você está usando (para mim, o padrão é "Abrir por extensão de arquivo"

Passo 4:
Certifique-se de que a opção Gerar todos os arquivos csproj esteja marcada e a Anexação do Editor esteja marcada

Etapa 5:
Abra o script C # que você estava tentando abrir anteriormente

Espero que isto ajude

Atualmente usando
- Unity 2019.3.3f1 Pessoal
- Visual Studio 2019 [/ QUOTE]
Origado, resolveu meu problema.

 

There are several solutions here that will work to restore Intellisense functionality using Visual Studio and VSCode editors. However, I believe in my experience that the quoted method above is the true answer to the problem. The reason being, VS and VSC won't recognize the namespaces and other Unity Engine internals and keywords without having a Solution associated with the C# script file. I have no idea what causes this, but it simply won't recognize Unity engine namespaces, classes etc without it. In step 4 above, when you hit "Open C# Project" from the right-click context menu on a C# script file, this tells the selected editor to open a legit *project* for the source code - so, if there is previously no ".sln" and related items for the said project, it will default to creating them in the appropriate directory on your file system.

As a sort of catch-all for anyone experiencing this problem, the summary of the solution to the entire issue is thus:

1. Open Unity. In the editor, click on Window -> Package Manager.
   1. Scroll down the list of packages and ensure the Visual Studio Editor and/or the Visual Studio Code Editor packages have a green checkmark next them (meaning, they are installed).
2. In the Unity editor, click on Edit -> Preferences to bring up the Preferences window.
   1. Click on the External Tools option.
   2. At the top of the right column in the window, you should now see an option for External Script Editor. Ensure that it does NOT read "Open by file extension." Instead, you will want to choose the correct version of Microsoft Visual Studio 20[xx] or Microsoft Visual Studio Code that you have installed on your machine.
   3. Ensure that everything under "Generate .csproj files for" is checked to true.
   4. Just to be certain they're all up to date, click the Regenerate Project Files button.
3. If your issues persist, close Microsoft Visual Studio and in the Unity Editor, click Assets -> Reimport All. After Unity reloads, find the script file in your project that you were wanting to work with, right-click it and choose the Open C# Project option from the context menu.

Again, there may be other issues as stated above for this problem. Maybe you as the user do not have the correct Packages installed/enabled in the Unity editor? Double check that. As of this writing (Aug 16, 2021) there does not seem to be any Unity Debugger extension for Visual Studio 2019; I double checked (though there may be for VSCode, so feel free to look that up just in case). If you feel that Visual Studio is not geared for use with Unity, you can always double check it by opening the Visual Studio Installer program, click Modify, and then ensure that under the "Gaming" subsection, the "Game Development with Unity" check box is checked true. You'd of course then click the Modify button if you made any changes, and make sure while you have it open that you're using the latest version.

I know it was a bit wordy, but I hope this summary further helps anyone else turning to this thread for issues regarding Intellisense not functioning between Unity and Visual Stuido or Visual Studio Code. It was written as of Unity 2021.1.16f1, and Visual Studio 2019 (VS 2022 is yet in Beta)!

 

I was also having the same issue that IntelliSense was not working. I am currently using Unity 2021 and using Visual Studio Code as my IDE. What I did was that I went into settings in Visual studio > Text Editor > Suggestions and then I enabled Inline Suggest (I'll include a screenshot) and then Intellisense began working.

 

Bro idk how to thanks you. You just fin the solution i was searching for hours.
God bless you and make you steve Job
Anas

 

Thank you so much !

 

Life saver... This type of people undoubtedly go to heaven c:

 

Trust me or not but you are a life saver. Thanks pal. Appreciate your work.

 

thank you thank you and thank you. this was driving me crazy not having intellisense not working

 

That worked, thanks!

 

OMG so much time waisted on this issue.... after doing most hints I read here, I had to do one more step. I hope it will be helpful for the others newcomers ;-)

1. Open any script from within Unity so that visual studio opens.
2. Locate solution explorer - for some reason, i had it hidden on the right side of my screen (not my standard layout)
3. Right click on your solution and select Resolve Errors

This fixed my problem. Good luck!

 

Thanks so much exactly what was needed.