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.

How should I manage custom package.appxmanifests and auto-generated projects?

When building a Unity project in a clean environment, I need to modify the package.appxmanifest it generates to set up my extensions. Once this is done, what should be checked into Git so that the next person who pulls down the project also picks up the custom manifest?

Should the auto-generated solution that's produced by Unity be checked in?
Or is there a way in the Unity project itself provide a custom manifest so that it gets used if the project is built in a clean environment?




  • My initial push to git usually includes the unity project setup, the .net setup, and the app manifest tweaks. I guess just get used to managing large total files sizes for unity projects. I have some embarrassingly large skunkworks projects in VSTS that push and pull no problem, just takes a few minutes vs a few seconds. You could google 'unity gitignore' to find some good ignore templates.

    Maybe something simple like this:

    1. Please see my post for some setup notes and tips.
    2. Run the HoloToolkit scene & project settings commands from the menu.
    3. Build the project, open the solution, and make your app manifest tweaks.
    4. Set your Release-->x86-->Remote Machine and your device IP.
    5. Get a full working deploy.
    6. Finally, commit & push changes for others to pull, if things are setup correctly the repo may be large but things should work.
Sign In or Register to comment.