I haven't tried it as 1.23.0 is working for me, but I guess the thing to do is reload the latest (currently 1.23.9), and set that setting and see what happens. Then change "Omnisharp: Use Global Mono". The setting can be found in VSC: go to File > Preferences > Settings > Extensions > C# Configuration. You can change it back yourself to "eGlobalMono": "always" which should fix your scenario.". This however is incompatible with Mono-based development e.g. NET Core 3.1 SDK isn't supported by any current Mono release, so the setting "eGlobalMono" has been changed to "never" in 1.23.1 (see changelog ). There is some information in the github Omnisharp issues list here which may be relevant. It might be, or it might be that the add in has tightened up how it does something, and Unity has fallen foul of it. Not sure if this means a problem with Omnisharp or not. What made the difference was reverting the version of Omnisharp C# for Visual Studio. Intellisense, syntax checking etc is all OK, and debugging works. With Unity 2019.3.14F1, Visual studio code 1.52.1, C# for Visual Studio 1.23.0 (Omnisharp) the problem has not so far reappeared. (This is why I do not want to move from Unity 2019.3.14F1 to 2020.whatever at the moment - you never know what might happen). #Visual studio code editor package unity how to#I am wondering if anyone has met this before and knows how to fix it? I am not very familiar with the workings of VS Code, but I assume it must be reading the Unity project file to do intellisense etc. I realise this is almost certainly as VS Code related problem, not Photon, but Photon.Pun is the only bit it objects to. The problem is VS Code thinking there are errors. The code however is just as it was - it does not come up with any compile errors in the Unity editor itself, and it all runs fine, including the networking Photon parts. The error says "the type or namespace name 'Pun' does not exist in the namespace 'Photon' (are you missing an assembly reference?)". The instant result of this is that there are all sorts of compilation errors showing up in VS Code relating to my multiplayer code interfacing with Photon. Stupidly, I took Microsoft's advice to update VS Code, and its version went to 1.50.1. #Visual studio code editor package unity for mac#The VS Code version was 1.48.3 - and everything was fine - no compile errors, all code working OK etc. On macOS: Visual Studio for Mac 2019 version 8.9 or newer with Visual Studio Tools for Unity 2.0.9 or newer. The Unity version is 2019.3.14F1 - I know there are later, but I don't want to move forward just yet in case of 'unexpected problems'. I am developing Unity game apps on a PC using C#, running Visual Studio Code as the editor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |