Welcome to our official discussion site. You’ll find topics on features, bugs, development, and general support here
https://www.noesisengine.com/forums/
That should solve the pesky #if UNITY_blahblah#endif for using directions. Only one such Imports.cs file in the project, having one such #if and the rest of the project is fine.It will now be possible to create a single file with namespace imports that are used everywhere. For example, if there is a popular namespace that is used in virtually every file, say Microsoft.Extensions.Logging.ILogger, then it will be possible to add a global using Microsoft.Extensions.Logging.ILogger to any .cs file (I suggest the Program.cs or a dedicated Imports.cs) and the logger interface will be available in the entire project. Not the solution! Nobody can predict which imports are needed anywhere, so they are grouped per project.
Yeah, that could be perfect for Noesis. It would help us to properly implement #1790.Could this be a solution for you guys? This should allow you to get those code behind things added.
https://devblogs.microsoft.com/dotnet/i ... enerators/