locked
XAML Parsing Failed in Windows Store App (KinectV2) RRS feed

  • Question

  • Hi all,

    i am trying to create a Windows Store App (Windows 8.1) that can be controlled by the user through a KinectV2 Sensor, but i am experimenting a really basic problem with the application: if i add an item of type KinectRegion to the xaml, Visual Studio raises a (not too much helpful) XAML Parsing Failed error, and underlines the KinectRegion.

    Here you can find my really simple xaml:

    <Page
        x:Class="Windows_App.Screen.MainPage"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:local="using:Windows_App.Screen"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        xmlns:kinect="using:Microsoft.Kinect.Xaml.Controls"
        mc:Ignorable="d">
    
        <Grid x:Name="RootWindow" Background="#45B6E7" >
            <kinect:KinectRegion></kinect:KinectRegion>
        </Grid>
    </Page>

    The strangest thing is that the IntelliSense suggests and allows me to autocomplete the insertion of the KinectRegion, and i can find the KinectRegion item it in the Toolbox items list.

    Any idea on what problem is going on here?


    Wednesday, February 4, 2015 4:43 PM

Answers

  • The KinectRegion is already added via the app.xaml.cs page. You don't need to add the region as it is dynamically added to any page.

    Carmine Sirignano - MSFT

    • Marked as answer by Marco Suriano Monday, February 16, 2015 9:37 AM
    Friday, February 13, 2015 8:15 PM

All replies

  • What are your solution/project settings in Visual Studio? Are you targeting x86/x64 not ARM or Any? Additionally, I am assuming you added the correct reference/extension for Windows 8.1(VS2013). When adding the reference/extension the correct platform extension to use will have Microsoft.VCLibs, version=12.0 in the details when you click on the entry.  

    Carmine Sirignano - MSFT


    Thursday, February 5, 2015 6:37 PM
  • Hi Carmine,

    yes, i am targeting an x86/x64 platform (i have tried both) in my Solution and, as you can see from the image, i am also using a Kinect Reference that has "Microsoft.VCLibs version=12.0" in the details. But the XAML Parsing Failed still occurs.



    Monday, February 9, 2015 9:38 AM
  • Do the samples work? If its an issue with the SDK install those should fail as well. What is the Active Platform for the solution project when trying to build?

    Carmine Sirignano - MSFT

    Monday, February 9, 2015 8:07 PM
  • Where can i find the sample projects for the Windows Store App SDK? I tried the ones for the WPF technology, and they work great ( i have another project written in WPF that uses a KinectV2 without any problem).

    My active platform (for the moment) is x64, as shown in the picture below.

    (Anyway, thanks for all the support you are giving to me in order to solve this strange problem! :) ) 

    Tuesday, February 10, 2015 11:38 AM
  • Any applications marked "XAML" in the SDK browser are for windows store. You need to click the Install button to copy the code and compile it. Because store application have to be side loaded or deployed through the store to run, we provide the full source project to compile and deploy.

    Additionally, you can have a look at the getting started to ensure you follow the steps as documented: https://msdn.microsoft.com/en-us/library/dn799310.aspx


    Carmine Sirignano - MSFT

    Wednesday, February 11, 2015 6:49 PM
  • I have tried to follow your suggestions, but the error persists. I have loaded the ControlBasic-XAML example from the SDK Browser but, when i try to add a KinectRegion to the XAML, i still receive the error XAML Parsing Failed, as you can see in the image.

    Thursday, February 12, 2015 2:16 PM
  • The KinectRegion is already added via the app.xaml.cs page. You don't need to add the region as it is dynamically added to any page.

    Carmine Sirignano - MSFT

    • Marked as answer by Marco Suriano Monday, February 16, 2015 9:37 AM
    Friday, February 13, 2015 8:15 PM
  • That's a good news! I thought it could be a dll problem, but evidently it was not so! :)

    Thank you again for your support!

    Monday, February 16, 2015 9:37 AM