Why when i open a new script in visual studio the MonoBehaviour is not in light blue ?

I marked with red circle what i mean it's not in light blue:



And marked in blue circle this example to show how it is suppose ot be:




In the editor in the Project > Assets > My Scripts > Ladder > mouse right click Create > C# Script give it the name Raise then double click but i can't use it since the MonoBehaviour is not active not in light blue.
Other scripts have it fine.

Not sure what is wrong. I tried to give it other names like RaiseLadder or Raise Ladder but each time i create the script it's not working.

 

Its a bug with VS and Unity. Sometimes the VS intellisense just breaks. Usually deleting the Library and the .csproj/.sln files fixes the issue. These folders get recreated by Unity upon reopening the project.

 

Sometimes the .cs file will be opened as a single file that has not been registered properly in the project file yet, hence your assembly references and other source files are not accessible from the newly created script.

I can only speak about personal experience, but for me, this mostly (or even exclusively) happens when I use 'Enter' on a newly created script. Double click does usually work like a charm and triggers a solution-reload dialog as soon as VS gets focused again.

Once you run into this problem, it is usually enough to close VS and re-open with Unity. If that doesn't fix it right away, you still got the option that @TaleOf4Gamers has mentioned.

 

It caused by Renaming Project Folder after project creation.
Simple Solution: Rename your project file to original.
Boring Solution: After you create your script, go to VS and find your newly created script in the solution explorer panel. Right click and choose "Exclude from Project". Then right click your Assets folder on solution explorer, select Add context, and then select "Existing Item" option. Then choose and add your newly created script file from this window. That fixes the problem. But still you have to do that for every single script.

 

Hello. I think this post is relatively old. Please excuse me for my english. I seem to have found the solution to this problem.
Right click Assembly-CSharp in the solution explorer and click unload the project. Then redo the same manipulation but this time to reload the project. Alleluia it works again ;-)

 

I add this problem today; I just quit both Unity and VS and restarted them and the problem solved itself.

I hope this will be fixed in future versions.

 

I generally only hit weird issues like this when I create a new CS file and try to open it before Unity has finished recompiling from the change.

 

I'm afraid this is not the reason; I just created a script and opened it about 30 seconds after creating it and the problem is there. It doesn't take that long to Unity to compile a new empty script.

Only fix: closing VS and restarting it.

 

I think generally VS with Unity has bad synchronization.
I didn't hit issue as yours. But VS desyncing is not something uncommon for me.
So there may be something else going on.

Try in Unity Ctrl+R tor refresh, after script is created.
Or create script from VS. And copy, or type MonoBehaviour manually.

 

They ve fixed it, download latest Tools for Unity and Visual Studio 2017, there is a post in VS forums stating so. Anyway for me it does not happen anymore.

 

I'm already using VS 2017 and the latest tools for Unity and the latest 2018.2 Unity: it's not fixed.

 

Here is a quicker workaround I fixed.

Problem:
Visual Studio 2017's intellisense doesn't recognize new MonoBehaviour scripts in generated from Unity.

Workaround:
Right-click the project in VS and unload the project (shortcut-L), right-click again and load it (shortcut-L again).

All MonoBehaviour scripts created hereafter no longer require the workaround. Visual Studio magically recognizes newly created scripts! I don't understand why, but it works.

 

It is i! A random Necromancer passing by, i actually fixed this problem in Unity and Visual Studio Link, the monobehaviour not being highlighted.

I fixed it by Unity > Edit > Preferences > External Tools > External Script Editor > (Change it to) Visual Studio 2017 (Community)

then restart both programs.

 

If I recall correctly, this was happening with Visual Studio already. The problem seems to have been fixed with the most recent versions of Unity; I haven't seen it happening in 2018 or 2019 yet.

 

Thanks a bunch for the solution.

 

Thanks for the solution.but i found before i saw you 3 minute later. T T

 

THANKS FOR THAT, searched for hours, many thanks!

 

If you don't have Visual Studio 2017 as an option, go to Start (Win10), type Visual Studio, right click on your preferred version (2017), select 'open file location', right click on the 'Visual Studio 2017' shortcut and select properties. Copy the full Target path without double quotes. Close out of these windows and get back into Unity.

Unity > Edit > Preferences > External Tools > External Script Editor > Browse

then paste your full path in without quotes and hit Open. You should now see the friendly name for "Visual Studio 2017". Close out of Preferences and double click your script file. Should open as expected now.

Thanks to everyone that came before me.

 

This worked for me, didn't restart unity (VS was already closed).
NB: Using VS 2019

 

THanks so much dude!!!

 

I FIX IT THANKS YOU

 

What a god! Thanks man!

 

This was the only solution that worked for me. Thank you!

 

You are the best person alive, my beloved friend. Good luck to you and your whole family, you've made my day.

 

YES! I need to read all the answers (and the one with the most likes) before searching for hours trying the first ones. Thank you sooo much! I was losing hope.

 

I tried on Unity 2020.1.0b11 none of the above worked on MacOS Catalina. By right-clicking on any of the the c# scripts in the project folder and selecting "Open C# Project", then I could double click going forward any script in the project folder and intellisense picked up all monobehaviour. Hope that helps

 

Many thanks kind sir, this worked for me. You saved me from crazyness.

 

A Good Necromancer Wellplayed

 

THIS IS THE SOLUTION - BRIAN SULLIVAN

 

Knoxx014 thank you, I've been looking for hours.

 

TY TY TY

 

Old thread. But I'd just like to say thank you to this guy! Solution worked like a charm!

 

Thanks mate, it's working

 

This is the fix that worked for me. The problem started after the latest updates to Visual Studio and unity on 9/1/2020

 

Hey folks, PM of Visual Studio Tools for Unity here. If you're reading this post with similar issues, I am sorry for the trouble! Here are some things to consider trying first:

Note*: If you're using Unity 2020, the integration with Visual Studio is handled by a Unity Package. Make sure this is up-to-date by visiting the Unity Editor > Windows > Package Manager. Search for the "Visual Studio Editor" package. Update it to version 2.0.2 (latest at this time). If you're using Unity 2019, there is no Unity Package to use for installation and can skip this.

A common workaround for problems like this is to regenerate the project files. Close Visual Studio. Then, go to Unity Editor > Preferences > External Tools and click the Regenerate project files button. Next, go to Unity Editor > Assets > Open C# Project.

If you're using Visual Studio 2017, I strongly urge you to consider installing Visual Studio 2019 for the latest improvements and feature updates to the integration for Unity. If you're using Visual Studio for Mac, consider getting the latest updates from the Check for Updates menu.

If you're still having trouble like this, please use the Help > Report a Problem menu from Visual Studio or Visual Studio for Mac and document what's happening. Our team is eager to troubleshoot the remaining issues causing behavior like this. Please DM me if you are willing to troubleshoot this directly.

 

I am unable to get the 'Unity MonoBehavior scripting wizard' to work using the CTRL-SHIFT-M combo. Is this outdated?

 

@armystone,

Please log an issue via the Help > Report a Problem menu in Visual Studio. That keybinding is still valid, but you might be hitting a different issue preventing it.

 

Thanks, also for me who use Unity 2020 this solution worked!

 

Thank You So Much It worked in VS 2019.

 

It really worked!! Thanks a lot, man!!

 

I am not able to open the project after deleting the Library and ProjectSettings.

 

Just adding in that this solved my problem! A note that it did not work until I restarted both programs, and that I had to type in 'Monobehavior' again.

 

Great, your fix worked for me too. Thanks!
Unity (2019.4.19f1) with 2019 (vs community) as well.
Without specifying this option, only one c# source file would open, no solution, no intellisense for "MonoBehaviour" for example.

 

[QUOTE = "knoxx014, publicación: 4283710, miembro: 2783350"] ¡Soy yo! Un Nigromante al azar que pasaba, de hecho solucioné este problema en Unity y Visual Studio Link, el monocomportamiento no estaba resaltado.

Lo arreglé con Unity> Editar> Preferencias> Herramientas externas> Editor de scripts externos> (Cambiarlo a) Visual Studio 2017 (Comunidad)

luego reinicie ambos programas. [/ QUOTE]

 

esta es la buena!

 

Thank you.
This one worked for me.

 

1. In the visual studio go to solution Explorer
2. In Assets hierarchy look for exactly folder that your script placed on that . probably you can't see the script in its folder under solution explorer hierarchy !
IF YES then
3_1. Right_click on exactly the mentioned folder select Add > Existing Item look for missing script in your unity project and add it . one click on some place of your script on VS editor . every thing must be OK .
ELSE IF you see the script
3_2. Right_click on the script delete it and re_add it .

 

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

https://forum.unity.com/threads/intellisense-not-working-with-visual-studio-fix.836599/

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

Also, this: https://forum.unity.com/threads/no-suggestions-in-vscode.955197/#post-6227874

 

What helped for me was inside Visual Studios on the right hand side in Solution Explorer, an assembly wasn't loaded correctly. Right click on it and say reload and it should possibly fix some of you guys' problems.

 

Thank you, words cannot describe my gratitude.