Looks like at least one of the reported issues was due to building ARM, which was being picked by Visual Studio by default given its alphabetical ordering.
It's likely some of the other issues are due to running the slower Debug builds, which are unlikely to work well on HoloLens in these scenarios, and which Visual Studio seems to always pick as the default configuration.
Looks like at least one of the reported issues was due to building ARM, which was being picked by Visual Studio by default given its alphabetical ordering.
It's likely some of the other issues are due to running the slower Debug builds, which are unlikely to work well on HoloLens in these scenarios, and which Visual Studio seems to always pick as the default configuration.