Unity visual studio code не показывает ошибки

5

Сообщений: 3 • Страница 1 из 1

NOVA

Адепт

 

Сообщения: 1722

Зарегистрирован: 17 май 2011, 11:45

Откуда: Дядя Саша from Mother Russia

1max1

Адепт

 

Сообщения: 5430

Зарегистрирован: 28 июн 2017, 10:51

NOVA

Адепт

 

Сообщения: 1722

Зарегистрирован: 17 май 2011, 11:45

Откуда: Дядя Саша from Mother Russia

Сообщений: 3 • Страница 1 из 1

Visual Studio ships Unity analyzers out of the box, which trigger custom warnings when something looks wrong with your C# code. If you are using Visual Studio Code, however, you will need to set these up manually to get the same warnings.

Begin by following this guide to configure Unity to run with Visual Studio Code.

Due to how Unity handles its .csproj files, it does not seem possible to install packages automatically. You will need to download the analyzers from the NuGet website manually. When you’re done, open the package file using a tool such as 7zip and extract Microsoft.Unity.Analyzers.dll onto your project’s root folder. You can place it inside a folder named NuGet, for example. Do not place it inside Assets or Packages, as that will cause Unity to try to process the .dll which will make it output an error in the console.

Next, create an omnisharp.json file at the root folder of your project, as explained here. Analyzer support in Omnisharp is experimental at the moment, so we need to enable it explicitly. We also need to point it to the .dll file we just extracted. Your omnisharp.json file should end up looking like this:

    {
    "RoslynExtensionsOptions": {
        "EnableAnalyzersSupport": true,
        "LocationPaths": [
            "./NuGet/microsoft.unity.analyzers.1.9.0"
        ]
    }
}

Where "./NuGet/microsoft.unity.analyzers.1.9.0" is a relative path pointing to the folder containing the .dll file. Depending on where you placed it, your path may look different.

Congratulations! The Unity analyzers should now be working in your project. You can test them by creating an empty FixedUpdate() method inside one of your MonoBehavior classes, which should trigger a The Unity message 'FixedUpdate' is empty warning (UNT0001).

Note that while it is possible to activate these analyzers, the supressors they ship with the package (that turn off other C# warnings that may conflict with these custom ones) may not be picked up by Omnisharp at the moment, according to this thread. You can still turn off specific rules manually, by following these steps:

1. Create a .editorconfig file in your project’s root folder (next to Unity’s .csproj files)

2. Add the following contents to the file:

    root=true

[*.cs]
dotnet_diagnostic.IDE0051.severity = none

root=true tells Omnisharp that this is your project root and it should stop looking for parent .editorconfig files outside of this folder.

dotnet_diagnostic.IDE0051.severity = none is an example of turning off the analyzer with ID IDE0051 by setting its severity level to none. You can read more about this here. You can add as many of these rules as you wish to this file.

[*.cs] indicates that our custom rules should apply to all C# scripts (files with the .cs extension).

Thanks for your attention and if this was useful to you consider following me on Twitter!