The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
Certification to publish HoloLens App to Store
Anyone else encounter / fix this certification error for key containers in publishing their HoloLens app?
Perhaps authors of HoloLens apps already on the store could provide info?
@jbienzms is there someone on the HoloLens team at Microsoft that can provide insight?
ERROR from Visual Studio 2015 R3
Severity Code Description Project File Line Source Suppression State Tool
Cannot import the following key file: DigiCertIFI20170215TY.pfx. The key file may be password protected. To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key container name: VS_KEY_E00FCBB792A0AB94 myapp Build
I am using this configuration to package a HoloLens App for the store:
- Unity 5.5.0f3
- Visual Studio 2015 R3
- Digicert Authenticode Code Signing Certificate (works running app on HoloLens)
- Unity Windows Store XAML build
- Building Master version
- Running on HoloLens Hardware
What are the best practices for publishing HoloLens Apps including this certification process? What is the WACK and where is it for certification?
Closest thing I have found are these:
I have published apps for iPhone, with certification, and it was time consuming but not as convoluted as the current process for HoloLens apps on Windows Store. There are many windows types for code signing (Authenticode, Strong Naming, etc.) , and it is not clear what is needed for most common path using Visual Studio, UWP, and HoloLens together. For instance, only Internet Explorer 11 seems to work for the certificate download and exporting the downloaded pfx file. Also the certutil.exe and sn.exe along with other tools and which ones are relevant to publishing HoloLens apps are not clear.