Open ImmanuelBaskaran opened 4 years ago
Hi, I found this issue before, you are right, it caused by the Unity testing, I added the unit testing in the last commit, it used the assembly reference, which will break the build, you could find another branch in GitHub (Lens/Build-Branch), I removed the testing stuff in this branch, and verified it could be built successfully Because the testings were added in the last phase of the project, so we didn't have much time to fix the build failure.
There is another issue we have opened. In the last phase of the project, we deployed all components on AKS. After replacing the local URL to the Accessor with the AKS endpoint, some connectivity issue occurred. In Unity editor, the application works well, but when you deploy the build version into hololens device, you can not get the hologram data from the url (AKS endpoint), we didn't fix this issue becasue we don't have much time.
When I pulled the repository and tried to build the project as per the instructions. The build fails with a Unity Exception.
I found one line that helped identify the issue Catastrophic failure while running rrw: Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'nunit.framework, Version=3.5.0.0, Culture=neutral, PublicKeyToken=2638cd05610744eb'
From this I determined that the script HoloStorageConnectorTest.cs was causing the trouble as was using using NUnit.Framework; Is there a way to install NUnit for unity 2018, or is the only workaround to delete the test?