Note that there are some explanatory texts on larger screens.

plurals
  1. POMany errors "Not exist in namespace"
    primarykey
    data
    text
    <p>I'm new to c#,visula studio and kinect development. I'm trying to reconstruct the microsoft example "Interaction Gallery" ,included in the kinect sdk 1.8. I have import all the xaml and the classes that need to run the project into a new project, but maybe i have miss something... I receive many "not found in namespace" error, an example is in this code :</p> <p>App.xaml</p> <pre><code>&lt;Application x:Class="WpfApplication1.App" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:converters="clr-namespace:Microsoft.Samples.Kinect.InteractionGallery.Converters"&gt; &lt;Application.Resources&gt; &lt;ResourceDictionary&gt; &lt;ResourceDictionary.MergedDictionaries&gt; &lt;ResourceDictionary&gt; &lt;converters:NegationConverter x:Key="NegationConverter" /&gt; &lt;converters:InvertibleBooleanToVisibilityConverter x:Key="InvertibleBooleanToVisibilityConverter" /&gt; &lt;converters:MultiplicationConverter x:Key="MultiplicationConverter" /&gt; &lt;converters:InvertibleBooleanToPromptStateConverter x:Key="InvertibleBooleanToPromptStateConverter" /&gt; &lt;ExponentialEase x:Key="ExponentialEasingFunction" EasingMode="EaseInOut" Exponent="2.0"/&gt; &lt;LinearGradientBrush x:Key="BackgroundGradientBrush" StartPoint="0, 0.5" EndPoint="1, 0.5"&gt; &lt;GradientStop Color="#E6E6E6" Offset="0.0" /&gt; &lt;GradientStop Color="#FFFFFF" Offset="0.5" /&gt; &lt;GradientStop Color="#E6E6E6" Offset="1.0" /&gt; &lt;/LinearGradientBrush&gt; &lt;SolidColorBrush x:Key="KinectPurpleBrush" Color="#FF511C74"/&gt; &lt;/ResourceDictionary&gt; &lt;ResourceDictionary Source="ViewDataTemplate.xaml" /&gt; &lt;ResourceDictionary Source="Common/StandardStyles.xaml"/&gt; &lt;ResourceDictionary Source="Controls/KinectButtonStyles.xaml" /&gt; &lt;ResourceDictionary Source="Controls/PromptControlStyles.xaml" /&gt; &lt;ResourceDictionary Source="Controls/TransitioningContentControlStyle.xaml" /&gt; &lt;ResourceDictionary Source="Controls/VideoPlayerStyle.xaml" /&gt; &lt;/ResourceDictionary.MergedDictionaries&gt; &lt;/ResourceDictionary&gt; &lt;/Application.Resources&gt; </code></pre> <p></p> <p>I receive the error in those lines:</p> <pre><code> &lt;converters:NegationConverter x:Key="NegationConverter" /&gt; &lt;converters:InvertibleBooleanToVisibilityConverter x:Key="InvertibleBooleanToVisibilityConverter" /&gt; &lt;converters:MultiplicationConverter x:Key="MultiplicationConverter" /&gt; &lt;converters:InvertibleBooleanToPromptStateConverter x:Key="InvertibleBooleanToPromptStateConverter" /&gt; </code></pre> <p>The error is: </p> <blockquote> <p>Name "NegationConverter" not found in namespace "clr-namespace:Microsoft.Samples.Kinect.InteractionGallery.Converters"</p> </blockquote> <p>There's a strange thing...when i write this piece of code, converters:NegationConverter is suggested by the autocomplete function of VisualStudio. What does it means? What i can check to find what's wrong? The way i have used to import the interactionGallery parts to my project is: VisualStudio solutionExplorer->Add Existing item (i have repeat this step for each resource that i had need to import)</p> <p>EDIT</p> <p>No progress with this trouble, i had rewirite all my code, i have tried to export to new project each file,each class of the InteractionGallery sample. It must work, maybe there's some settings that i have left, the framework target is the same , and properties tab seems to be identical. However i receive the same errors.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload