Issue With. Net core install/read

Unity Courses Ask
#1

Hi,

I just picked up the 2D unity course yesterday and am trying to set up my macbook pro with all the necessary installs as per the early tutorials.

I (believe) I have followed all the troubleshooting steps on the tutorial (installed, correct path, restart machine etc,) but am still getting the error message:

The .Net Core SDK cannot be located. .Net core debugging will not be enabled… etc.

Can you please help? I’m new to this, and don’t want to carry on assuming this is fine, and it generate problems later on.

Thanks
Graham

#2

Hi Graham,

Please follow the instruction on this website and make sure all required extensions are installed: https://code.visualstudio.com/docs/other/unity

If the issue persists, please check the console of VS Code (not Unity!). If the .NET Framework 4.7.1 (Developer Pack) is mentioned there, download and install it from the official Microsoft. Here is the link: https://dotnet.microsoft.com/download/dotnet-framework/net471

Depending on your version of Unity, it might be that you will have to install the “Visual Studio Code Editor” package in Window > Package Manager in Unity.

  1. Press Ctrl + Shift + P in VS Code.
  2. Type “OmniSharp: Select Project” and press Return.
  3. Select the solution workspace entry.

Maybe you’ll have to reboot your computer. Then launch Unity again and open one of your scripts.

Did this help?

See also:

#3

Hi Nina,

Thanks for getting back to me. Yeh I’d actually tried all that you suggested, though I did it a few times to be sure… But the problem still persists.

Do you think it may be to do with the fact that Visual Studio has a specific program for MacOS and some of the extentions/plugins whatever the right terminology is aren’t supported by the presumably older VS Code programme? If so, I don’t mind using the specialised VS programme, but I suspect it wont quite look/work the same as what is visible in the tutorials and is likely to lead to confusion/frustration.

Any help you can offer would be gratefully received.

Thanks
Graham

#4

You could try to set omnisharp.global to always. See the following link. I mean “always”, though, not “never”.

By the way, Visual Studio and Visual Studio Code are two different programs. Which one do you use? Maybe I linked the resources for the “wrong” program.

#5

Hi Nina,

Sorry for the delay in responding, I’ve been distracted with dayjob stuff. I’ve come back to the programme and its now fine. Not sure what step did the trick, but its working at thats good enough for me. Thanks for your help.

Graham

#6

Thanks for the update. If the issue is fixed, don’t worry about it anymore. :slight_smile:

#7

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.

Privacy & Terms