Deprecation of support for the .Net Scripting backend used by the Universal Windows Platform

I guess this didn't make it in 2018.2.13f1 already? ;-)

 

Just wanted to ping this, as I'm still running into this and having the debugger ip and port in the output really makes things easier. With 2018.2.18f1 it seems I still need to manually patch the IL2CPP source, or is there a better solution available?

 

Hmmm, in fact, I can't seem to attach the managed debugger manually anymore. Should the steps shown above still be the same?

 

What's the planned version for the .net deprecation? In many of our HoloLens UWP projects we're trying to use SignalR or WebRTC, and IL2CPP is breaking both of them, either with just silently failing or object marshaling issues.

For a WebRTC sample try https://github.com/flufy3d/webrtc-uwp-sdk/tree/WebRtcUnity/common/windows/samples/PeerCCUnity - works with .net backend but fails with IL2CPP.
With SignalR just try any new asp.net core signalr sample - while calling to the server works, server->client calls fail.

 

We are also still having issues enabling debugging, just updated to 2018.3.3f1 and performing the same steps as above, with VS Unity Tools 3.9.03 and Visual Studio 15.9.6. We are able to find the instance of HoloLens to attach to after it has deployed but cannot connect to it, the cursor spins for a second and then does nothing as others like charlie and shaddad described.

This is rather unfortunate since the latest Vuforia assets which we are using seem to only work with IL2CPP as the backend, on top of the build iteration times and additional steps compared to before. According to Vuforia this is a regression that will be fixed, but until we solve this issue developing using the IL2CPP backend without breakpoints in addition to the extra hassle is obviously unreasonable. I'm sure this is likely on our end, but am looking for what could potentially be the cause. Should we update to 18.3.4?

 

Thank you, our issue was from a fresh project with capabilities enabled in Unity but not in the generated VS project manifest. Although we will probably use .NET backend when we are able to again for build iteration's sake, this helps for our current development while the regressions are fixed.

 

I submitted a report for the webrtc issue, there's a link within that contains a repo with everything needed to set it up. (sadly it's not trivial) case 1126463.

I'll try to submit the SignalR issue as well but I need some time to make a demo project for that.

 

I found a great example implementation for communication between the Unity part and the native UWP code for the .NET scripting backend under https://bitbucket.org/Unity-Technologies/windowsstoreappssamples.
I tried to refactor the code to a cpp-UWP app so i can use this communication for a il2cpp build of my Unity application (the example is based on .NET and therefore a c#-UWP app).
I could do most of the coding, but the most interesting part, accessing GameObjects and their components, i could not find any API documentation.
For example in the MainPage.xaml.cs the methods of the Communications class:

Code (CSharp):

1. public static void SetCubeMaterialColor(byte r, byte g, byte b)
2.         {
3.             UnityEngine.GameObject go = UnityEngine.GameObject.Find("Cube");
4.             UnityEngine.Material mat = go.GetComponent<XAMLConnection>().material;
5.             mat.color = new UnityEngine.Color32(r, g, b, 255);
6.         }

Is there some documentation i could not find?
Or can someone point me to the right direction?

Thanks in advance.