Question Private member 'xxxx.Start' is unused

using VS code and update dotnet runtime to 7.0.9, encounter the above prompt, and how to fix it?

 

It's just a warning and not an actual error. You can safely ignore it.

Not used VS Code but the Unity integration for Visual Studio prevents this from showing up. Mind you it's worth noting support for VS code has been dropped by Unity.

 

As Spiney notes, the VSCode extension has been deprecated and abandoned:

https://forum.unity.com/threads/update-on-the-visual-studio-code-package.1302621/

There may be a community fork available that is receiving updates.

https://github.com/Chizaruu/com.tsk.ide.vscode

Also, this: https://forum.unity.com/threads/no-suggestions-in-vscode.955197/#post-6227874

This may help you with intellisense and possibly other Visual Studio integration problems:

Sometimes the fix is as simple as doing Assets -> Open C# Project from Unity. Other times it requires more.

Other times it requires you also nuke the userprefs and .vsconfig and other crufty low-value high-hassle files that Visual Studio tends to slowly damage over time, then try the above trick.

Barring all that, move on to other ideas:

https://forum.unity.com/threads/intellisense-not-working-with-visual-studio-fix.836599/

Also, try update the package inside of Unity: Window -> Package Manager -> Search for Visual Studio Editor -> Press the Update button

Depending on flavor and version of Visual Studio, it may also have an installation step that you perform within the actual Visual Studio. This step seems finicky at best and may require multiple openings of VS before it comes up.

 

Yes this is very weird. It's just started happening with me today. I also saw somebody else complaining about it on Github.

Call me paranoid, but I suspect it's connected to Microsoft releasing a new update and Unity Tech attempting to coerce us into updating to a more recent version of Unity.

 

Your suspicions are correct. Microsoft's extension doesn't yet support these methods.

https://forum.unity.com/threads/mic...-for-visual-studio-code.1468913/#post-9197576

 

Please make sure you are using the latest VS Editor package 2.0.20 (which now supports VSCode as well), and the Unity extension in VSCode. We ship analyzers that will add Unity-specific diagnostics or remove general C# diagnostics that do not apply to Unity projects (like IDE0051). If you see them, you configuration is perhaps incomplete.