First published on MSDN on Nov 08, 2018
Debugging Unity projects with a .NET backend is rather easy. Unfortunately, it's deprecated at will go away and some point in the future.
Then there is IL2CPP. It's considerably faster and even build times seems to be quicker to me. However, debugging was not possible or only became available for the player.
That is, until 2018.2.x.
But let's start from scratch.
Happy debugging!
Debugging Unity projects with a .NET backend is rather easy. Unfortunately, it's deprecated at will go away and some point in the future.
Then there is IL2CPP. It's considerably faster and even build times seems to be quicker to me. However, debugging was not possible or only became available for the player.
That is, until 2018.2.x.
But let's start from scratch.
-
Set up your Unity project build settings and enable
Development Build
,Script Debugging
andWait for managed debugger
- Build in Unity, open the solution in a VS.NET instance and deploy it to a remote device
-
The build and deploy takes considerably longer and once deployed you're asked to attach the debugger
-
Open a new VS.NET instance from Unity and select
Attach Unity Debugger
from the drop down
-
You should be prompted with a window that allows you to select the lens. (It should also work when the lens is attached via USB, but you might need to enable inbound UDP communication for
devenv.exe
)
Happy debugging!
Updated Jan 15, 2019
Version 2.0mplogas
Microsoft
Joined May 10, 2018
Modern Work App Consult Blog
Follow this blog board to get notified when there's new activity