Major instability modifying XAML in split view from VS11

Question

1. Create a new C#-based Metro-style application
2. Edit MainPage.xaml in split view (i.e. designer surface and XAML). This should already be opened after creating the project.
3. In the LayoutRoot grid, paste this XAML fragment:

   <ListView x:Name="lstvTest" HorizontalAlignment="Left" Height="496" Margin="35,100,0,0" VerticalAlignment="Top" Width="308"
      ItemsSource="{Binding Fred}">
   </ListView>
   

4. Save MainPage.xaml without closing.
5. Copy this text to the clipboard: Source={StaticResource Fred}
6. Highlight "Fred" in value of the ItemsSource attribute by double-clicking the text.
7. Paste the text that you copied to the clipboard (i.e. CTRL+V).

VS11 will show as not responding for several minutes. In some cases, Windows itself will become non-responsive. Trying to bring up Task Manager with CTRL+ALT+DEL will take a long time, and when it finally comes up, you'll see CPU at 100%.

Answer 1

I was unable to reproduce this. I created a new Application project and followed your steps. After step 7 I had the following Xaml:

    <Grid x:Name="LayoutRoot" Background="#FF0C0C0C">
        <ListView x:Name="lstvTest" HorizontalAlignment="Left" Height="496" Margin="35,100,0,0" VerticalAlignment="Top" Width="308"
   ItemsSource="{Binding Source={StaticResource Fred}}">
        </ListView>
    </Grid>

The ItemsSource was squiggled that "The resource 'Fred' could not be resolved." but VS was immediately responsive. These are both as expected.

Can you confirm that there aren't any other steps necessary? Were you using the full VS Developer Preview or the Express version? 

You can also report this directly via the Feedback tool.  That will also capture some logs from your system which may be helpful if this is a system specific problem. You can also try to capture a dump of the hung VS and include that.  There have been a number of fixes made to the Xaml designer, so this may have been fixed; however, without being able to reproduce it I can't tell if it is a known issue or not.

--Rob

Answer 2

I was using the full VS Developer Preview. I will use the Feedback tool. Thanks!