That’s great news, I had no idea!! Better start working on it then 
Mazyod
AlejandroHuerta
I’ve been using your library, @Mazyod, with BestHTTP and it’s been working out great so far in local development. I’ve debated using the official .NET implementation of websockets, perhaps later. I’ve also wrapped your library to be able to use async/await. Is there anything you need help with to convert to .NET4.5+?
1
Mazyod
Awesome, glad to hear it’s been treating you well! 
Honestly, I just didn’t prioritize the migration, since Unity will only release an experimental version of 4.6+ support. If you can help out, that would be awesome!
The main good thing to be covered is the SynchronizationContext, to remove the need to plug in a callback handler, and synchronize everything with the main thread within the library instead.
Right after that comes the support for async/await, for nicer APIs to handle the replies and whatnot. I’m not sure yet how asyc/await can work with different results, like “ok”, “error”, … etc, but could be a fun challenge to design properly.
0
AlejandroHuerta
Yeah I understand. I’ve run into some bugs with 4.6 profile so far.
SynchronizationContext is already set up for us so as soon as you call await it’s implicitly captured by Unity’s context. As for the return value the way I handled it is by essentially returning your Reply class and handling the status myself. Not sure there’s a better way to design that.
I’ll see if I can write up a PR this month.
1