# There are red lines everywhere

**URL:** https://discussions.unity.com/t/there-are-red-lines-everywhere/938721
**Category:** Scripting
**Tags:** Scripting, Bug
**Created:** [January 28, 2024, 4:13pm UTC](https://discussions.unity.com/t/there-are-red-lines-everywhere/938721 "2024-01-28T16:13:33Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Kurt-Dekker](https://dub1.discourse-cdn.com/unity/user_avatar/discussions.unity.com/kurt-dekker/32/101578_2.png) [@Kurt-Dekker](https://discussions.unity.com/u/Kurt-Dekker)
#### Post date: [January 28, 2024, 6:42pm UTC](https://discussions.unity.com/t/there-are-red-lines-everywhere/938721/3 "2024-01-28T18:42:41Z")

</div>

You can fix your own typing mistakes. Here’s how:

Remember: NOBODY here memorizes error codes. That’s not a thing. The error code is absolutely the least useful part of the error. It serves no purpose at all. Forget the error code. Put it out of your mind.

**The complete error message contains everything you need to know to fix the error yourself.**

The important parts of the error message are:

- the description of the error itself (google this; you are NEVER the first one!)
- the file it occurred in (critical!)
- the line number and character position (the two numbers in parentheses)
- also possibly useful is the stack trace (all the lines of text in the lower console window)

Always start with the FIRST error in the console window, as sometimes that error causes or compounds some or all of the subsequent errors. Often the error will be immediately prior to the indicated line, so make sure to check there as well.

**Look in the documentation. Every API you attempt to use is probably documented somewhere. Are you using it correctly? Are you spelling it correctly? Are you structuring the syntax correctly? Look for examples!**

All of that information is in the actual error message and you must pay attention to it. Learn how to identify it instantly so you don’t have to stop your progress and fiddle around with the forum.

**If the error is only in the editor and NOT in Unity, then read here:**

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:

> [@Intellisense Not Working with Visual Studio (Fix)](https://discussions.unity.com/t/778503):
>
> Likely, if you have appeared here to this page you are having the problem I had for the past hour or so. Intellisense is not working in Visual Studio. Well lucky for you, I figured out the solution to fix this issue after searching the entire web. So you don’t have to search the web anymore, I will tell you how I fixed the issue. Step 1: Close Visual Studio Step 2: In Unity, go to Edit \< Preferences \< External Tools (left part of the Window) Step 3: In External Tools go to the part that sa…

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 on the Visual Studio Code package](https://discussions.unity.com/t/886480):
>
> Hi everyone, We want to update you on the state of the Visual Studio Code for Unity package. This plugin was a result of one of our hackweek experiments by a few of our former employees. Unfortunately, it’s never been fully functional and hasn’t received any updates for almost two years, bringing you an unstable coding experience. We want to be open with you about its state so that you know what to expect. The scripting team has huge projects in the works with a significant impact for a major…

Update: the VSCode integration is back… maybe!?

> [@Microsoft previews Unity extension for Visual Studio Code](https://discussions.unity.com/t/925353):
>
> We are delighted to announce that Visual Studio Code support for Unity is coming back in a new improved form. In June our friends at Microsoft launched the C# dev kit, which gives Visual Studio Code users access to some of the powerful C# tools more familiar to full Visual Studio users. Today, they are opening a preview of the [Unity Extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=visualstudiotoolsforunity.vstuc) which brings the Unity experience for Visual Studio into Visual Studio Code. The extension supports code editing powered by Roslyn…

There may be a community fork available that is receiving updates.

> **[GitHub - Chizaruu/com.tsk.ide.vscode: Enhance your Unity development workflow with...](https://github.com/Chizaruu/com.tsk.ide.vscode)**
>
> Enhance your Unity development workflow with seamless code editor integration for VSCode.

Also, this: [No suggestions in Vscode](https://discussions.unity.com/t/805330/7)

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.

---

_[View the full topic](https://discussions.unity.com/t/there-are-red-lines-everywhere/938721)._