Mixedrealitytoolkit-unity: Building UWP in all versions of Unity not working for Visual Studio 2017 15.3

[StephenHodgson]

Be advised, do not update visual studio to 15.3!
See https://github.com/Microsoft/MixedRealityToolkit-Unity/issues/833

There is a compatibility issue between Unity and upcoming Visual Studio 2017 update 3 when targeting UWP, using .NET scripting backend (IL2CPP scripting backend is not affected) and building generated Visual Studio project.

Read full details here.

Here is the status of patches with the fix:

• 5.5 version with the fix: 5.5.4p5 (not released yet)
• 5.6 version with the fix: 5.6.3p2
• 2017.1 version with fix: 2017.1.0p5
• 2017.2 version with fix: 2017.2.0b7

Potential Work Around.

[jessemcculloch]

This is a duplicate of #833

[StephenHodgson]

Not exactly, more of a report that there was an issue, where this issue details the cause and soon resolution.

I was under the impression that it only affects 2017.2, but it instead affects all current versions of the editor.

[jessemcculloch]

Gotcha. Interesting that it's the exact same error message.

[StephenHodgson]

2017.2.0b7 Released with a fix for VS 2017 15.3 building.

Known Issues:

• Asset Pipeline: Reverting changes on applied prefab crashes Unity (825035)
• Editor: Unable to export a Unity package (938223)
• Windows: [WSA] Error messages appear while/after building a project with "Unity C# projects", if the Editor folder contains a script. (918989)
• Windows: [XR][WSA] Including "Unity C# Projects" while building to Universal Windows Platform, causes builds to fail (927925)
• XR: Hololens / UWP / PS4 VR Devices not yet supported with the new input system for VR use.
• XR: New API surface for recent UnityEngine.VR.WSA.Input changes has forthcoming breaking changes to land in another beta soon.

[hencohen3]

I have vs 2017 15.3 and i download the 2017.2.0b7 Released you suggest now I have build problems with

using UnityEngine.VR.WSA;   The type or namespace name 'WSA' does not exist in the namespace 'UnityEngine.VR'. Are you missing an assembly reference?

[ThmsMsqrt]

@hencohen3 try to change UnityEngine.VR.WSA to UnityEngine.XR.WSA

[hencohen3]

@ThmsMsqrt i change to UnityEngine.XR.WSA but now im getting a lot of errors(i attached image) . the build is successful but when i try to run for exmple the "cursor" scene in the hololens the build and deployment is successful but i cant see any thing in the hololens.

Any idea?

[StephenHodgson]

Only use the 2017.2 Dev branch with the 2017.2 unity editor.

[hencohen3]

@StephenHodgson what do you mean? to download vs 2017.2 and to stay with the unity 2017.2.0b7 ?

[StephenHodgson]

I'm saying we've already done the work to get the 2017.2 Dev branch working in the 2017.2 unity editor and to test that, instead of upgrading the 2017.1 branch.

For the master branch you'll need to wait until Unity releases a patch for the 2017.1 editor.

[Zod-]

They've pushed back the versions for when this will be fixed as the the new patch is for the security update. e.g. 5.6.3p1 was just released but the fixed version was pushed back to 5.6.3p3

5.5 version with the fix: 5.5.4p5 (not released yet)
5.6 version with the fix: 5.6.3p3 (not released yet)
2017.1 version with fix: 2017.1.0p5 (not released yet)

[genereddick]

I can't seem to find any working combination of Visual Studio, Unity and HoloLens Toolkit. -- things were fine prior to updating VS

I've tried VS 2017.3 and 2017.3.1 with Unity 2017.1.n and 2017.2.0b7 and 2017.2.0b8 and HL 2017.1 master & 2017.2 with no luck but maybe I'm missing something.

Is there one set of those that definitely works, or is rolling back VS to 2017.2 the best bet?

[StephenHodgson]

A nice little discussion on the unity forum.

An interesting workaround.

[joekellyms]

Just tried this workaround today, and it worked for me:
https://forum.unity3d.com/threads/net-scripting-backend-and-visual-studio-2017-3-incompatibility.487833/#post-3191224
I also didn't have re-do the fix after building again. It must keep that file if you build to the same location.

[StephenHodgson]

Finally a fix! 2017.1.0p5 released

https://github.com/Microsoft/MixedRealityToolkit-Unity/issues/849#issuecomment-324979531

[StephenHodgson]

Unity relesed a patch for 5.6.3p2