.NET Core Issues

Running a final application built by UnigineEditor via the Build Tool does not require .NET Core SDK or .NET Core runtime. The output applications are self-contained and can be run flawlessly on almost any computer.

We recommend installing the version 3.1.300: https://dotnet.microsoft.com/download/dotnet-core/thank-you/sdk-3.1.300-windows-x64-installer.

Download the required installer and run it following all installation steps.

Optional: After installing the SDK you might find it useful to disable .NET Core SDK telemetry.

We recommend installing .NET Core SDK version 3.1.300: https://docs.microsoft.com/en-us/dotnet/core/install/linux.

Linux operating systems supported by .NET Core include at least the following:

• Red Hat Enterprise Linux 7, 8
• CentOS 7, 8
• Fedora 31, 32
• Debian 9, 10
• Ubuntu 16.04, 18.04, 19.10, 20.04
• openSUSE 15+
• SUSE Enterprise Linux (SLES) 12 SP2+, 15
• Alpine Linux 3.9+

.NET Core SDK can be installed on Linux in a number of ways. We describe manual installation, as it is more flexible (the process was described by Michael Heydt). Using the command line terminal, do the following:

1. Download the installer:
   Shell commands

   wget https://download.visualstudio.microsoft.com/download/pr/0c795076-b679-457e-8267-f9dd20a8ca28/02446ea777b6f5a5478cd3244d8ed65b/dotnet-sdk-3.1.300-linux-x64.tar.gz

   For RedHat Enterprise Linux 6 users the following line should be used:
   Shell commands

   wget https://download.visualstudio.microsoft.com/download/pr/cdb98822-bf8f-4f11-a5a4-baa8d8ad66d0/b696896552ca7768a7189f775e220d2e/dotnet-sdk-3.1.300-rhel.6-x64.tar.gz -O dotnet-sdk-3.1.300-linux-x64.tar.gz

2. Create the directory and uncompress the file there:
   Shell commands

   mkdir ~/dotnet-3.1.300 && tar -xvf dotnet-sdk-3.1.300-linux-x64.tar.gz -C ~/dotnet-3.1.300

3. Create a symlink to the executable file in that directory:
   Shell commands

   sudo ln -s ~/dotnet-3.1.300/dotnet /usr/bin/dotnet

   You can do without a symlink and root access — just edit the ~/.profile file (or its equivalents: ~/.bashrc, ~/.kshrc, ~/.zshrc) in any text editor by adding the following line:
   Source code

   export PATH="$PATH;$HOME/dotnet-3.1.300"

   It will look this way:
   
   Then re-login. If UnigineEditor still doesn't detect .NET Core SDK, restart the system.
4. Optional: After the file has been unpacked successfully, you can delete the archive:
   Shell commands

   rm dotnet-sdk-3.1.300-linux-x64.tar.gz

5. Optional: After installing the SDK, you might find it useful to disable .NET Core SDK telemetry.

1. Open the Command Prompt (Click the Start button and type cmd).
2. In the window that opens, type the following:
   Shell commands

   dotnet --list-sdks

The following information should appear:

1. Open the terminal.
2. In the window that opens, type the following:
   Shell commands

   dotnet --list-sdks

The following information should appear:

In case IntelliSense cannot be started due to the spawn cmd ENOENT error in the OmniSharp extension, it is recommended to add %WINDIR%\System32 to the PATH variable.

On Linux, you may require adding ~/.vscode/extensions to the path, for example in the .bashrc file:
export PATH=$HOME/.vscode/extensions:$PATH

For more details see https://github.com/OmniSharp/omnisharp-vscode/issues/32.

In case a single source file of a C# component is opened in VS Code when double-clicking it in UnigineEditor, it is recommended to make sure the path to the VS Code bin (%VSCODE_INSTALLATION_FOLDER%\bin) folder is added to the %PATH% environment variable, for example, as follows: C:\Program Files\Microsoft VS Code\bin.

For Windows, it is also recommended to restart the PC to have the %PATH% variable updated.