I have no idea how this happened last night but I’m currently running into this issue with VS Code Editor. Classes are not being detected whenever Unity & C# Dev Kit is enabled in Extensions. I have tried reinstalling VS Code as well as Unity but still running into the same issue.
Fixed by installing the oldest version of VS Code.
Which Unity version and which VSCode package? Unity’s support for VSCode is gone and MS’ new package is in preview.
Btw, VS Community got just about one tenth of the issues of VSCode in case you want to get any real work done.
I’m really set on using 2019.4.161f just because of the compile times. Visual Studio Code 1.81. I believe there is something going on with Omnisharp because Unity Intellisense isn’t working either. I’ve tried reinstalling Unity as well as VSC.
Also it just makes no sense why it would randomly stop working as it always did in the middle of the night…
2023-08-28 00:08:16.670 [warning] The project file 'c:\Users\bill\Mechanics\Assembly-CSharp.csproj' is in unsupported format (for example, a traditional .Net Framework project). It need be converted to new SDK style to work in C# Dev Kit.
2023-08-28 00:08:16.763 [info] Project system initialization finished. 0 project(s) are loaded, and 1 failed to load.
2023-08-28 00:08:16.772 [error] Failed to load project 'c:\Users\bill\Mechanics\Assembly-CSharp.csproj'. One or more errors occurred. (This project is not supported in C# Dev Kit.)
Found this error inside the output window.
Hmmm perhaps the version of VSCode you use is „too new“. Basically it cannot read 2019 style csproj anymore, at least seems like a possibility.
In any case, if you want to build for mobile or webgl using 2019 is not a good idea due to min. required SDK versions for mobile, and generally outdated webgl tech. For PC it ought to be okay.
@billygamesinc You need to use the VS Editor package v2.0.20 in your Unity project, then properly select VSCode as your external editor.
You are currently generating legacy-style csproj where VSCode+Unity&C# Dev Kit are requiring the new SDK-Style. Updating your VS code package will take care of that.
I tried this method but it didn’t work, I managed to fix it by reverting my C#DevKit to an older version.