Porting existing Unity Project to UWP - Workflow issues

Target Platforms Desktop
1

Hi,

We are beginning the process of porting an existing Unity Windows app to UWP. Our code uses several .Net namespaces that don’t exist in UWP (we don’t know how many yet - large code set.) So obviously the build to produce the UWP project is breaking. I am wondering what a good workflow is to discover what existing code needs to be modified to migrate to UWP. There don’t seem to be any code analyzers out there. It would be nice if Unity had an option to build the UWP solution including errors so we could open the solution in VS 2017 and see everything that needs to be modified. Does anyone have a thought on a workflow or tools that will be efficient?

Thanks

2

I mean - you can’t build something that doesn’t compile so you’re kinda stuck there…

Beyond that - I’d start here: https://docs.unity3d.com/Manual/windowsstore-missingtypes.html

3

Ya, I think we have come to the conclusion that we will have to create a Unity new project, pull in scripts one (or many) at a time to see what breaks, and fix as we go. One workaround for anyone else wondering is building an empty Unity UWP solution (I suggest including your folder structure and a few working scripts) and then adding all of your scripts to that solution. Then you can see everything that breaks all at once. Still tedious though.