Search code examples
unity-game-enginehololensmrtk

How to Deploy a unity working app to the HoloLens 1?

I have followed some guidelines found online on how to build a unity application using MRTk2 and saw which bugs to ignore, nevertheless, after building my solution I am unable to deploy it to the HoloLens 1.

I built the solution using:

  • II2Cpp backend & have
  • installed SDK 10.0.18632.30
  • Set minimum SDK to 10.0.10240.0
  • Target SDK to Latest Installed

And The build succeeded!

When I open the solution on Visual Studio 2017, and try to deploy(release, x86) I get the errors bellow:

  • Error MSB3073 The command ""D:\Project\Virtual%20Guided%20Assembly%20V3\Code_VGA.v3b\Builds\WSAPlayer\Il2CppOutputProject\IL2CPP\build\il2cpp.exe" --libil2cpp-static --compile-cpp -architecture=x86 -configuration=Release -platform=winrt -outputpath="D:\Project\Virtual%20Guided%20Assembly%20V3\Code_VGA.v3b\Builds\WSAPlayer\build\bin\Win32\Release\GameAssembly.dll" --data-folder="D:\Project\Virtual%20Guided%20Assembly%20V3\Code_VGA.v3b\Builds\WSAPlayer\build\bin\Win32\Release\" -cachedirectory="D:\Project\Virtual%20Guided%20Assembly%20V3\Code_VGA.v3b\Builds\WSAPlayer\build\obj\il2cppOutputProject\Win32\Release\" -generatedcppdir="D:\Project\Virtual%20Guided%20Assembly%20V3\Code_VGA.v3b\Builds\WSAPlayer\Il2CppOutputProject\Source" --additional-defines=WINDOWS_UWP --additional-defines=UNITY_UWP --additional-defines=UNITY_WSA_10_0 --additional-defines=UNITY_WSA --additional-defines=UNITY_WINRT --additional-defines=PLATFORM_WINRT -dotnetprofile=unityaot -verbose --map-file-parser="D:\Project\Virtual%20Guided%20Assembly%20V3\Code_VGA.v3b\Builds\WSAPlayer\Il2CppOutputProject\IL2CPP\MapFileParser\MapFileParser.exe"" exited with code 3.

  • Error MSB4018 The "GetOutOfDateItems" task failed unexpectedly.

Here is a picture of my environment for a better understanding of my problem

Solution

  • After many trials, I have decided to move the project to a new location and I was able to build it and deploy to the HoloLens. Apparently the problem was being caused by the encoded space "%" on the project path, removing that allowed me to build and deploy the application successfully!

    You can see the difference on how the solution were being loaded into VS17 in the picture below: