Recently I started using Rider for Scripting in Unity. It's fine but when I switch to some script (very small weight), it doesn't show any code highlighting (except blue):
The same code in other script which can work:
For work reasons it is not possible for me to delete the current script. I've tried to reinstall and checked my Settings, but still couldn't fix it.
EDIT: Thanks for the note, here is my other information:
Unity Setting:
Preferences - External Tools - External Script Editor - Rider 213.6461.51
Open Script:
Double-click on the script in Unity to open it
Same script, each keyword is highlighted in VS Studio 2019
My Unity version is 2018.4.1f1, Rider version is 2021.3
Does anyone know how to solve this problem?
I have solved the problem.It appears that Rider updates the naming conventions when opening certain scripts.
The immediate solution is：Suppose one of your script files has code highlighting disabled, Open the script in Rider, and you will see the word OFF in the upper right corner.Click it, you will see:
enter image description here
All you have to do is change "None" to "All Problems".
Related
Maybe I am just missing something, but I don't get how to setup a blank solution in VSCode (Under Windows or Visual Studio, you are able to just create a new Blank NanoFramework Template, but how can I do that in VSCode :/). I would really like to work with the nanoframework instead of c/c++, but I don't know how to create a blank solution :(.
That option is not currently available.
The main goal of the VS Code extension is to allow (partially) folks on MAC or Linux to work with .NET nanoFramework.
It's not possible to debug on VS Code and you'll only have a full experience on Visual Studio. If you're on Windows, the recommendation is to use Visual Studio.
The issue is VS code doesn't see UnityEngine.UI library.
I had this issue before and I solved like it this:
I changed the code editor in preferences to Visual Studio, regenerated files and launched c# project. On the start, vs created needed .csproj files and then I closed vs and changed it back to vs code and it workeed.
However, now I am working on another project and I encountered same issue, I tried the method I described above but it didn't work.
Any ideas?
So, after days of tinkering and trying different solutions I found on the internet I finally found out how to solve it (all by myself).
Switch to VS and make sure it detects the UnityEngine.UI library. Then don't close VS, switch to VS Code, don't hit "regenerate files", launch c# project, enjoy!
These steps covered several possible issues:
https://stackoverflow.com/a/70977258/6046022
(just an overview, follow the link for the complete steps)
downgrade VSC package
re-install Unity UI
regenerate files
When I highlight a file and hit F2, the file is normally replaced with an edit box where you can rename it.
After a few seconds, the edit box goes away and you need to quickly type the different file name (every time). I'm not sure what could cause this - any idea?
I'm on Ubuntu 20.04.1 LTS, Visual Studio code 1.52.1
Thanks
This looks like a bug reported in a few issues since v1.52 that all point to this one:
https://github.com/microsoft/vscode/issues/111652
also https://github.com/microsoft/vscode/issues/112555 and https://github.com/microsoft/vscode/issues/112438
It is reported in 111652 as fixed in the Insiders' Build. Can you test it there? I can't reproduce in Stable Build, W10.
I am developing Unity game apps on a PC using C#, using Visual Studio Code as the editor. The apps are targeted at PC and Android. Multiplayer uses Photon Pun 2.
The Unity version is 2019.3.14F1 - I don't want to move forward just yet in case of 'unexpected problems'.
The VS Code version was 1.48.3 - and everything was fine, no compile errors, all code working OK etc.
Stupidly, I took Microsoft's advice to update VSC, and VS Code went to 1.50.1. Result of this is that there are all sorts of errors showing up in VS Code relating to the Photon code. All these errors stem back to the 'using Photon.Pun;' line. It says "the type or namespace name 'Pun' does not exist in the namespace 'Photon' (are you missing an assembly reference?)".
The code however does not come up with any compile errors in the Unity editor itself, and it all runs fine, including the Photon parts. The problem is in VS Code.
I realise this is almost certainly as VS Code problem, not Photon, but I am wondering if anyone has met this before and knows how to fix it?
(This is why I do not want to move from 2019.3.14F1 to 2020.whatever at the moment - you never know what might happen).
I had the same problem. Installing different versions of VS Code / VS Community Edition didn't fix anything for me, but this did:
With the project open in VS Code, find all occurrences of
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
in *.csproj files, and replace them with
<ReferenceOutputAssembly>true</ReferenceOutputAssembly>
Tried rebuilding project files, swapping to a different editor (VS Community Edition 2019 - that was fine), but no difference - VSC persisted with the errors. Rest of intellisense working OK.
In the end, totally uninstalled VSC and reinstalled, and that sorted it out. No idea what the actual fault was.
I was wrong.
To-day, the errors are back.
The reason appears to be that in the process of trying to sort this, I installed VS Community Edition 2019 to see if that worked OK (it did). Then went back to VSC, and - that was fine too. Later I uninstalled VS Community Edition 2019 (it is taking about 4GB). It was uninstalling that which brought the errors back into VSC. Reinstalled VS Community Edition 2019, and it is all fine again.
So, VS Community Edition 2019 installs something that VSC needs - but I haven't yet figured out what it is.
UPDATE:
Gave up. Never managed to find out what VSC wanted and wasn't getting. Instead, reinstalled old version of VSC (1.48.2 from code.visualstudio.com/updates) and it is all fine again.
If still having this problem, all you have to do to fix it is by going to Package manager and install "visual studio editor package"
windows>Package Manager> All Packages /or Unity Registry (depeding on your unity version) search of visual studio editor
if it's already installed delete it and reinstall.
Got it FIXED!
Solution (it was a Unity issue):
In Unity, goto Edit > Preferences > External Tools > External Script Editor, and point it to Visual Studio..
Why this was so hard to find, I have no idea. But now my Photon solutions and namespaces properly transfer from Unity to Visual Studio. Hooah!
Also moved the script to where the photon scripts are
Uninstall the Visual studio community and re-install with latest VSC 2022. It will fix the issue
having assured myself that julia is enabled and that the linter is too (in vs code settings: Julia › Lint: Run), i get syntax highlighting on my xxx.jl script but no linting at all.
im on the latest vs code + latest julia 1.07 extension + latest macosx.
i did a clean installation of vs code, wiping all old related folders prior to installation (https://stackoverflow.com/a/53839847/11608725)
so julia is the only extension/package installed, no conflicts should be present.
what am i missing?
thanks!
edit/update:
i also found that i can NOT run an open script (via the leftmost button)
a pop-up says
and clicking on open launch.json gives
from which point on im pretty much stuck. googling around, a couple of very similar issues appeared (eg. https://stackoverflow.com/a/61284896/11608725, https://github.com/microsoft/vscode/issues/94725#issuecomment-612062020), but which should presumably have been fixed with vs code 1.44 and i am on 1.49.
perhaps the no-linting is related to this?
Have you tried Julia Formatter 0.3.0 for vs code? This has always worked for me.
similar message "Please first open a folder in order to .." pretty annoyingly appeared, my end, on a different platform [Win] [Visual Studio Code version: 1.56.2], too
meaning : it's likely the workflow/settings logic specific to VS Code, not an os/platform issue as such
all problems solved, my end, simply by
after launching VS Code
via "File" > "Open Folder..." : just do first -- before doing anything else in VS Code and/or with code-files -- open the current/working project folder [ie. the very folder with a ".code-workspace"-file in it for the given project (source file dir) ]