Entities and Api compatibility level .Net Standard 2.0. errors in console

After switching to api compatibility level .Net Standard 2.0 (from 4.X) I got a lot of errors in console pointing to
C:/Users/luvju/AppData/Local/Unity/cache/packages/packages.unity.com/com.unity.entities@0.0.12-preview.8/Unity.Entities.Properties/

e.g.
C:/Users/luvju/AppData/Local/Unity/cache/packages/packages.unity.com/com.unity.entities@0.0.12-preview.8/Unity.Entities.Properties/TypeInformation.cs(291,17): error CS0103: The name 'RefAccess' does not exist in the current context

I tried to clear cache and reimport assets, but it didn't help.
Please help to fix this

 

You need to set .net 4.x to use the ECS and Incremental Compiler packages

 

as zulfajuniadi stated, .net 4.x is a requirement of the entities package.

 

Well, Josh Peterson of Unity recommended me to set up api 2.0 because of my build size increase. (https://blogs.unity3d.com/ru/2018/07/11/scripting-runtime-improvements-in-unity-2018-2)
Guess he missed info about entites in my project.

Thanks everyone.

 

I think packages from Unity should be compatible with .NETStandard
especially since they are pushing for smaller runtime size

 

Burst, ecs, jobs simply can't work with .net3.5 (.net standard 2.0)

 

.net standard is not 3.5:

• 3.5 is the old runtime
• 4.6 is the new runtime. it has 2 options for api compatibilty level:
  • "full" .net framework 4.6 (has all the APIs in .net, but is heavier and not everything may be supported on all platforms)
  • .net standard 2.0 (it's designed to be lighter and fully cross-platform compatible, but it may not have some fringe APIs)

c# version is completely parallel to that (you can use some c#6 features in .net 3.5 like expression-bodied methods if you enable the compiler flag, and the incremental compiler enables c#7 in the .net 4.6 runtime)

old runtime also had the api compatibilty level option (.net 2.0 vs subset) except subset was arbitrary and broke almost every 3rd party library (e.g. json.net)
.net standard is (wait for it) a standard so most 3rd party libraries are expected to work with it