Unity Future .NET Development Status

It does compile now, but it crashes the process in runtime instead. Should I submit a new bug report or email them about the old one?

 

Can't use System.Collections.Immutable、Microsoft.Extensions.Logging... librarys(b6 \ b7).

 

Because of the System.Memory issue? It seems the issue is being investigated: https://forum.unity.com/threads/202...donlyspan-under-net-4-8.1152104/#post-7415969

 

If anybody wonders, I was told to open a new case, number 1357908.

 

Has anyone got it working? No idea how to add https://docs.microsoft.com/en-us/dotnet/csharp/roslyn-sdk/source-generators-overview

Code (CSharp):

1.     <ProjectReference Include="path-to-sourcegenerator-project.csproj"
2.                       OutputItemType="Analyzer"
3.                       ReferenceOutputAssembly="false" />

as csproj files are not used in build process. I've also tried https://docs.unity3d.com/Manual/roslyn-analyzers.html and csc.rsp -a but both didn't generate any code.

Directory.Build.props work but only for rider/vs not Unity build pipeline.

 

I made it work without much effort.
I used same method as with analyzer:
- create VS project;
- build dll;
- put it into Unity project;
- mark dll with RoslynAnalyzer label;

I see one problem with that Microsoft doc. They use Microsoft.CodeAnalysis.CSharp version 3.9.0 but Unity 2021.2 use Roslyn 3.8.0 (at least it was last time I checked). So it will not load such generator becouse it can't load all dependencies. To work with Unity generator should use version 3.8.0

 

What about?

 

I also got the source generators to work by building a dll in a different project.
Also, for a more convenient pipeline, I tried building it with Unity’s AssymblyBuilder and props file; Sadly, only the analyzers work for this solution while building fails when including source generators.

 

What did you do specifically to make it work?

 

I think he treated them like analyzers here:

Unity - Manual: Roslyn analyzers and ruleset files (unity3d.com)

 

Got it also working.

All platforms can be disabled, together with analyzer all required dlls have to be added, they can also have platforms and auto-reference disabled. These don't have RoslynAnalyzer label.

I even had to add System.Memory (net standard project) as somehow System.Collections.Immutable can't use included one.

 

Yep, I disable all platforms. also I disable auto reference and validate references.
I did not include any additional dll.
Additional dlls should not be required. Those dlls are part of compiler. Probably you have validate references enabled or something broken in latest Unity beta

 

I guess it depends on what generator uses. It didn't work without them.

 

Follow https://docs.unity3d.com/2021.2/Documentation/Manual/roslyn-analyzers.html and build the project with the following config:

Code (CSharp):

1. <Project Sdk="Microsoft.NET.Sdk">
2.  
3.     <PropertyGroup>
4.         <TargetFramework>netstandard2.0</TargetFramework>
5.     </PropertyGroup>
6.  
7.     <ItemGroup>
8.       <PackageReference Include="Microsoft.CodeAnalysis.Common" Version="3.8.0" />
9.     </ItemGroup>
10.  
11. </Project>

 

Since the .Net Framework setting doesn't really limit to .Net Framework, I'd suggest renaming it to Full or .Net Framework 4.8 + .Net Standard 2.1. Having it not specified in the dropdown leads to confusion like here with people saying that Span being present in it is a bug https://forum.unity.com/threads/2021-2-0b6-and-system-memory-readonlyspan-under-net-4-8.1152104

 

Sorry to quote you for something offtopic but, is there any chance you could "communicate" to the relevant management levels in Unity how happy we have been with your "style" of customer/community management? (I'm not expecting a concrete answer from you, just a "I'll see what I can do" is more than enough, thx).

Unfortunately other teams over on Unity have terrible communication skills/policies ranging from complete silence to bait-and-switch post and threads. Since from time to time Unity offers some "prices" for reporting bugs, participating in betas and/or interviews, I guess there is some level of interest from upper management in getting useful feedback.
But since feedback is a 2-way road, it seems a bit contradictory to have a "bug report contest with rewards" in one part of the forum and complete lack of unity staff interaction for half a year or more on others.

For anyone else reading this, "like" this post if u agree but try to refrain from actually posting as to limit the number of offtopic messages. I know I'm being selfish, but didn't want to pm Josh just for this.

 

The "Unity Success Team" & their "Success Advisors" have direct contact with Unity devs and report to higher-up as Unity uses them to take the 'pulse' of paying customers. Kinda as if 'marketing' were to tell direction that Dev-Team X/Y/Z is doing a good job.

Sending any, all, every type of feedback to them tends to reverbate up in the chain to other team-leads and managers from what I've seen. We have regular, scheduled meetings with them twice a year but can contact them anytime for anything - strongly encourage everyone to do the same in relation of Josh's team and the great job they're doing!

 

Using a .Net Standard 2.1 dll that references System.Runtime.CompilerServices.Unsafe via Nuget gives a MissingMethodException when any API from that is called. The editor should instead refuse to load such dll. Reported, case 1360423.

 

This is how UnrealCLR
https://github.com/nxrighthere/UnrealCLR
solved this:
https://github.com/natemcmaster/DotNetCorePlugins
for Net .5

Just FYI

 

Some questions about the state of .NET 6 support:

- Will the Unity support/update for .NET 6 be near the official release window of .NET 6 it self or later?
- Which Unity versions will support it?
- Which C# version will be supported? I hope the newest, which should be C# 10 once it is released?
- Will future C# / .NET updates be easier / faster after Unity supports .NET 6?

One additional question, I hope this is not off topic, but will Unity support the new official C# source generator feature, I think it is also planned to be released with .NET 6? (Currently still in preview)

 

Latest Unity 2021.2 beta already support it

 

@Jes28 Hi, would you happen to have resources on how to get started with those ?

 

https://forum.unity.com/threads/unity-future-net-development-status.1092205/page-6#post-7426526

 

@JoshPeterson what about csproj files support? I read some time ago that you were working or at least evaluating replacing asmdef files with csproj files.

This would provide native nuget support, native analyzers support, native source generators support, referencing non unity code .net projects without compiling them before, ...

 

Btw. The docs seems to be incorrect about native size integers not being supported, those are implemented as IntPtr/UIntPtr under the hood and require no runtime support. https://docs.unity3d.com/2021.2/Documentation/Manual/CSharpCompiler.html

 

@JoshPeterson I'm running into major problems using my organization's internal packages since .NET Standard 2.1 support has been added in 2021.1b6.

Until now I was using NuGet packages extensively via @xoofx's fantastic solution to which I have contributed several PRs: https://github.com/xoofx/UnityNuGet

In that repository if you don't know it converts NuGet packages to UPM format and adds the define NET_STANDARD_2_0 in each *.meta of each *.dll. This makes it very convenient to add NuGet dependencies in the UPM world.

But now I encounter several problems.

1. It is not possible to choose between .NET Standard 2.0 or .NET Standard 2.1.

With the following package for example it doesn't work because it only targets 2.0 and it brings the dependency "Microsoft.Bcl.AsyncInterfaces" which is not necessary in 2.1 but it should still compile in Unity because in a native .NET Core console project I can import it without any problem because it fallbacks to 2.0 target:

https://www.nuget.org/packages/AWSSDK.Core/

In this case it is a breaking change, since I will not be able to update any Unity project that uses @xoofx's UPM scoped registry.

2. NET_STANDARD_2_0 is defined instead of NET_STANDARD_2_1.

This is incorrect since we are in .NET Standard 2.1 and leads to confusion. If you have a Unity package with code that only compiles to 2.1 you cannot differentiate it from 2.0.

It is also confusing that in Player Settings it says ".NET Standard" without version number.

 

As you may have read in my previous post, NuGet support is something I've been pursuing and asking for on the forum for years but it never seems to be a priority for Unity.... Thanks to your solution I have been able to fix it until this b6 which has added support for 2.1 and broke everything.

Supporting *.csproj files would solve a lot of problems at once.

 

If you open the attached project on 2020LTS it works but if you open in 2021b it doesn't compile with the following error:

 

Assets\NewBehaviourScript.cs(9,9): error CS0433: The type 'IAsyncEnumerable<T>' exists in both 'Microsoft.Bcl.AsyncInterfaces, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' and 'netstandard, Version=2.1.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'

 

With the project I have attached in my previous message you can easily reproduce it by opening it in 2020LTS and then in 2021b where the compilation error will appear.

 

I can't without getting rid off @xoofx's UnityNuget automated setup and falling back to get all my NuGet dependency chain manually (+100 assemblies) downloading them one by one or checking one by one for this duplicities.

I know that if I pull all that dlls manually it works but what I'm saying is that .NET Standard it's backwards compatible on traditional .NET Core project, I don't understand why it isn't on a Unity project.

It's a serious breaking change for all people who are using .NET Standard 2.0 assemblies, it will break in cases like this. It's a very big problem because on 2021b it automatically updates to 2.1 without asking and it's not possible to go back to 2.0.

 

The problem is with the reference profile that Unity is using.

Here you have another NuGet package that would break (a package with millions of downloads):

https://www.nuget.org/packages/System.Text.Json

If you see it only targets .NET Standard 2.0 (no 2.1) and it depends on:

Microsoft.Bcl.AsyncInterfaces (>= 5.0.0)
System.Threading.Tasks.Extensions (>= 4.5.4)

Both dependencies are included with .NET Standard 2.1.

As I said on a traditional .NET Core project it works but on a Unity project it shows that duplicity error.

Another example:

https://www.nuget.org/packages/Microsoft.Extensions.Hosting.Abstractions/3.1.8

Only targets .NET Standard 2.0 (no 2.1) and it depends on:

Microsoft.Bcl.AsyncInterfaces (>= 1.1.1)

And also on this case I can't use the 5.x version of Microsoft.Extensions.* packages because of this issue I reported some time ago (only fixed on 2022alphas+): https://github.com/dotnet/runtime/issues/52990

 

It doesn't work so smooth with Unity becouse how Nuget dependencies resolve. Target runtime is selected for each package separately.

For example we have 3 packages:

• A - has netstatdard 2.0 and net 5.0
• B - depend on A and has netstatdard 2.0 and netstatdard 2.1
• C - depend on B and has netstandard 2.0 only.

We add package C to our program that target netstandard 2.1. Than our app will have C with netstatdard 2.0, B with netstatdard 2.1 and A with net standard 2.0.

So to simulate similar with unity we need to have multiple dlls for different targets with Define Constraints that will select dll depending on target runtime

 

Doesn't that mean that UnityNuget has to be updated?