I am building a library that I will be using in a Unity3D game, as well as on a server (we want to write once, use both places). The library would greatly benefit from being based off the .NET 4.5 profile as is the most recent prerelease of Xamarin (specifically async/await!)
When does Unity3D typically get these changes?
My take on it is that Unity uses Mono, and Mono mimics .NET. And Mono follows .NET, and Unity follows Mono. So Mono would have to support this first, then Unity would adopt that. In the past, this has been a very slow process. I have no idea when they intend to rev things again.
Thanks for the effort, but the reason I posted this is because MonoTouch will be supporting the .NET 4.5 profile in the next version (you can play with it now via the prerelease of Xamarin.iOS). I would like to know how frequently Unity pulls in those changes from "upstream"
– ssutch
Just a thought: since async/await relies on System.Threading, you won't be able to use it with any of the Unity functionality anyway - Unity requires all calls to UnityEngine and UnityEditor stuff to happen off the main thread. So, could you build your code externally to Unity and compile as a dll, then import your dll into Unity as a plugin?
– Julien-LyngeYou can schedule code to occur on whatever thread unity requires.
– ssutchSomeone with more programming experience will have to speak to this, but if you try to call it from, say, an Update(), I foresee bad things happening.
– Julien-LyngeWhat you'd end up doing is creating an inbox of sorts that processes incoming messages at an interval and dispatches that on the proper thread to any other objects in the graph.
– ssutch