Databases
StackOverflow2013
Postsdbo
POIssue with x:Name with XAML used between WPF and Silverlight
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIssue with x:Name with XAML used between WPF and Silverlight
    primarykey
    data
    text
    <p>I'm having a strange namespace resolution issue in my user control XAML files.</p> <p>If I create a new WPF library, it adds the following:</p> <pre><code>&lt;UserControl x:Class="UserControl1" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:d="http://schemas.microsoft.com/expression/blend/2008" mc:Ignorable="d" d:DesignHeight="300" d:DesignWidth="300"&gt; &lt;Grid&gt; &lt;/Grid&gt; &lt;/UserControl&gt; </code></pre> <p>This evaluates to a class name of MyLibraryNameSpace.UserControl1.</p> <p>However, if I add a Silverlight class library and add a UserControl to that application, I get the following XAML</p> <pre><code>&lt;UserControl x:Class="MyLibraryNameSpace.UserControl1" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:d="http://schemas.microsoft.com/expression/blend/2008" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" mc:Ignorable="d" d:DesignHeight="300" d:DesignWidth="400"&gt; &lt;Grid x:Name="LayoutRoot" Background="White"&gt; &lt;/Grid&gt; &lt;/UserControl&gt; </code></pre> <p>This evaluates to the same thing, but the XAML is different, so I can't have Silverlight and WPF projects referring to the same XAML since the x:Class statement would be correct for one and incorrect for the other. If I specify x:Class="MyLibraryNameSpace.UserControl1" in WPF it will be interpreted as MyLibraryNameSpace.MyLibraryNameSpace.UserControl1 under my current project.</p> <p>How do I get my WPF library to use fully qualified class names or otherwise resolve this scenario so I can use a single namespace for shared WPF / Silverlight code?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USchriga
    1. USMatt Eland
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. CONot sure if there's a way around this particular issue, but it's worth noting that WPF and Silverlight and really two completely different platforms that just happen to both use XAML to represent their UI content and have certain framework classes with the same names that behave similarly. I don't think it's advisable to use a single XAML file for both a Silverlight and WPF project, both for this reason and the other myriad incompatibilities that can crop up in how the two platforms interpret and use the XAML. If you're looking for something cross-platform, think Silverlight and OOB.
      singulars
      1. POIssue with x:Name with XAML used between WPF and Silverlight
      1. USDan Bryant
    2. COThanks. OOB isn't a possibility in this case since it's dealing with an existing WinForms / WPF app we wish to continue offering updates to the executable users are comfortable with.
      singulars
      1. POIssue with x:Name with XAML used between WPF and Silverlight
      1. USMatt Eland
    3. COIt just means it uses a different template for Silverlight. You don't need all the extra data per se.
      singulars
      1. POIssue with x:Name with XAML used between WPF and Silverlight
      1. USJonas Van der Aa
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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