Hello everyone.

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.
Options

Hololens app not builing since switching to VS2017 on Win10 Anniversary update

Hello, has anyone seen or gotten the below errors once switching to VS2017 why trying to build or deploy to Device:

Error CS0006 Metadata file '...\App\GeneratedProjects\UWP\Assembly-CSharp-firstpass\bin\x86\Release\Assembly-CSharp-firstpass.dll'

Error CS0006 Metadata file '...\App\GeneratedProjects\UWP\Assembly-CSharp\bin\x86\Release\Assembly-CSharp.dll'

Error The BaseIntermediateOutputPath must end with a trailing slash. Assembly-CSharp-firstpass

Error The BaseIntermediateOutputPath must end with a trailing slash. Assembly-CSharp

Answers

  • Options

    Visual Studio 2017 RC Release notes show a breaking change:-

    Starting in Visual Studio 2017 RC SDK, there is a breaking change with how Visual Studio consumes project and item templates in order to improve performance of template discovery. The new discovery mechanism now requires all item and project templates following "vstemplate" schema to be defined in template manifest files. Visual Studio templates that you do not define in a template manifest file will no longer be visible in New Project or New Item dialogs. While new VSSDK tooling will generate manifest during VSIX build time, if you have Visual Studio templates released as part of a MSI package, you must manually generate template manifest files for those templates

    So you wont be able to manually generate template manifest files for those templates.

    I suggest you follow the HoloLens load instruction
    sequence

  • Options

    Hi
    what does this mean, the instructions you linked to mention only 2015. Is 2017 unsupported for Hololens dev for now?

  • Options

    @christop,

    You're a pioneer here, Chris. You'll have to let us know if you can get 2017 working with HoloLens.

    James Ashley
    VS 2017 v5.3.3, Unity 2017.3.0f3, MRTK 2017.1.2, W10 17063
    Microsoft MVP, Freelance HoloLens/MR Developer
    www.imaginativeuniversal.com

Sign In or Register to comment.