Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've tried to reproduce your issue, but I couldn't. I have created the following WPF application:</p> <pre><code>&lt;Window x:Class="WpfBehaviorsTest.Window1" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:Interactivity="clr-namespace:System.Windows.Interactivity;assembly=System.Windows.Interactivity" Title="Window1" Height="300" Width="300"&gt; &lt;Grid&gt; &lt;Interactivity:Interaction.Behaviors/&gt; &lt;/Grid&gt; &lt;/Window&gt; </code></pre> <p>Everything works just fine before and after I compile my project. Could you test if this works for you? What version of MS Blend SDK do you use? What version of Visual Studio? Just to be sure: we speak about WPF application, not Silverlight, correct?</p> <p><strong>Update:</strong> You have exactly the same configuration as I do. The only problem is that it works here, but doesn't work on your side. Let's squash this insect by the following checks:</p> <ol> <li><p><em>What version of "System.Windows.Interactivity" assembly get's loaded by designer?</em> You could run another instance of MS Visual Studio and attach to the first VS process with "buggy"-designer. Go to Debug->Windows->Modules and check the version of System.Windows.Interactivity.dll. If it looks good you still can go and double check it with Reflector. Does it has <em>Interaction</em> class? Is there BehaviorsProperty in it?</p></li> <li><p><em>What exactly is happening there inside?</em> If assembly that we've checked in step 1 is correct, let's run heavy artillery. In fact I effectively use this approach quite often, whenever I have VS/Blend designer issues. Just run another instance of Visual Studio. Turn on breaks on all CLR exceptions (Debug -> Exceptions-> Check the box after CLR Exceptions). It might also help to turn on <a href="http://blogs.msdn.com/sburke/archive/2008/01/16/configuring-visual-studio-to-debug-net-framework-source-code.aspx" rel="nofollow noreferrer">.NET source code debugging</a>. Attach to the instance with invalid designer. Reload designer. Now, instead of seeing confusing message, attached Studio will bring us to the very heart of the Exception. What's there?</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POVisual Studio Designer broken using Expression Blend SDK Behavior
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAnvaka
    1. USAnvaka
    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. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis exact code does the problem for me. I'm using VS 2008 sp1, with Expression Blend SDK 3, in a WPF application. It compiles and runs, but when I open this xaml file in the VS Designer, I get the error.
      singulars
      1. PO
      1. USReed Copsey
    2. COThe error only occurs once loaded in the Designer window - the project compiles correctly. There is no error if loaded in the XML Editor (only the WPF Designer).
      singulars
      1. PO
      1. USReed Copsey
    3. COAnvaka: I really appreciate all of the work on this. It turns out it's due to a known issue that was addressed in KB958017.
      singulars
      1. PO
      1. USReed Copsey
 

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