Skip to content

Commit 1a831cf

Browse files
committed
Add note on csproj missing
1 parent 1e8a921 commit 1a831cf

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

Documentation/Tools/HolographicRemoting.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,19 +29,23 @@ If HoloLens 2 hand joints and eye tracking aren't working over remoting, there a
2929

3030
#### MSBuildForUnity package import via writing into the package.manifest
3131

32-
For the first point, the best way to check is to open Window -> Package Manager and make sure MSBuild for Unity shows up in the packages list. If it's there, assume this step succeeded. If it's not there, try running Mixed Reality Toolkit -> Utilities -> Configure Unity and repeat the steps above for running the MRTK Configurator.
32+
The best way to check is to open Window -> Package Manager and make sure MSBuild for Unity shows up in the packages list. If it's there, assume this step succeeded. If it's not there, try running Mixed Reality Toolkit -> Utilities -> Configure Unity and repeat the steps above for running the MRTK Configurator.
3333

3434
![MSB4U Package Manager](../Images/Tools/Remoting/MSB4UPackageManager.png)
3535

3636
#### DotNetWinRT NuGet package resolution
3737

38-
For the second point, the best way to check is to search the Assets folder for DotNetWinRT.dll. If this doesn't exist, navigate to the Assets folder in the Project view and select `[ProjectName].Dependencies.msb4u.csproj`. Assuming part 1 did succeed, there should be a custom inspector with Build, Rebuild, and Clean buttons. Try clicking Build or Rebuild, and then re-search for DotNetWinRT.dll. If that DLL now exists, this step succeeded.
38+
The best way to check is to search the Assets folder for DotNetWinRT.dll. If this doesn't exist, navigate to the Assets folder in the Project view and select `[ProjectName].Dependencies.msb4u.csproj`. Assuming part 1 did succeed, there should be a custom inspector with Build, Rebuild, and Clean buttons. Try clicking Build or Rebuild, and then re-search for DotNetWinRT.dll. If that DLL now exists, this step succeeded.
3939

4040
![DotNetAdapter Inspector](../Images/Tools/Remoting/DotNetAdapterInspector.png)
4141

42+
#### DotNetAdapter.csproj missing
43+
44+
If the previous step didn't succeed, it's good to double check that the appropriate csproj exists in your project. Check under MixedRealityToolkit.Providers / WindowsMixedReality / Shared / DotNetAdapter and check that DotNetAdapter.csproj exists. One common case where this file might not exist is if your .gitignore ignores csproj files and you've committed the MRTK files to a remote repo. In this case, please make sure you force add DotNetAdapter.csproj with `git add -f [path/to]/DotNetAdapter.csproj`, to make sure it gets committed and cloned for all other collaborators or machines.
45+
4246
#### `DOTNETWINRT_PRESENT` #define written into player settings
4347

44-
For the third point, navigate to the Unity Player Settings. From there, under the UWP tab, check under Other Settings for the Scripting Define Symbols. Make sure DOTNETWINRT_PRESENT is properly written in that list. If that's there, this step succeeded.
48+
Navigate to the Unity Player Settings. From there, under the UWP tab, check under Other Settings for the Scripting Define Symbols. Make sure DOTNETWINRT_PRESENT is properly written in that list. If that's there, this step succeeded.
4549

4650
![DotNetWinRT Present](../Images/Tools/Remoting/DotNetWinRTPresent.png)
4751

0 commit comments

Comments
 (0)