Unity package based on Unity Roslyn Updater to enable using C#11 features (including file-scoped namespaces) in Unity 2022.
Designed only to work on Windows.
Install from this git URL (see How to install from a git URL):
https://github.com/Alexejhero/Unity-CSharp11.git?path=Assets/UnityCSharp11
After installing, regenerate your C# project files - your project will now target C#11.
Please refer to the Language Support section of Unity Roslyn Updater's README to see which features of C#11 will work. C#12 features are not supported!
By default, Unity 2022 fails to detect MonoBehaviour or ScriptableObject classes from files which use file-scoped namespaces.
This package includes a patcher that modifies your local Unity Editor installation to fix this issue. Any other team members will also need to patch their editors to work with file-scoped namespaces.
A window will display at launch prompting you to patch the editor. After closing it, you can manually patch or unpatch again in Preferences > C# 11.
The patching process is reversible, so you may roll back at any time.
If you have Hot Reload installed, you will also need to install the package from this git URL:
https://github.com/Alexejhero/Unity-CSharp11.git?path=Assets/UnityCSharp11.HotReload
Hot Reload generates their own csproj files when compiling changes, and this package ensures they are also processed to support C#11.
This package automatically sets up csproj properties and compiler arguments for C#11, so you can remove any LangVersion modifications set in CsprojModifier.
This project was created as an alternative to Unity Roslyn Updater. Distributing the patcher as a Unity package makes it easy to install and use for all team members.
Unity Roslyn Updater replaces the editor's bundled Roslyn compiler (which, as of Unity 2022, supports up to C#11) with the latest version of the .NET SDK you have installed on your computer (if any). This allows Unity Roslyn Updater to support C#12 and beyond, but does not scale to multi-person teams due to the large possible variety of user environments - e.g. a developer using features that require a recent SDK would force artists to install that SDK to be able to compile the project.
For this reason, our package does not replace the compiler, so that all team members have access to the same language features.