RadDiagram automatic Design view switching

[Terry]

Is there any way to stop Visual Studio from switching to Design view every time a change is made to the XAML of a RadDiagram?!? So annoying!

[Petar Mladenov]

Hello Terry,

I have hit similar issue with VS 2012 but it is definitely very rare and hard to reproduce. We believe this is a bug in VIsual Studio rather that problem with RadDiagrams. Maybe there are possible solutions in MSDN forums, StackOverflow, etc.

Regards,
Petar Mladenov
the Telerik team

[Terry]

Thanks, Petar. Good to know I'm not the only one.

I can reproduce it consistently by simply adding or removing <Style></Style> in the <UserControl.Resources> tag of a UserControl with a RadDiagram defined in the UserControl. As soon as I comment out the <RadDiagram>, it stops switching to Design mode.

Uncomment the RadDiagram element, make a change to UserControl.Resources, and it starts switching back to Design mode.

<UserControl.Resources>
<Style></Style>
</UserControl.Resources>


<Grid>
<Grid.RowDefinitions>
<RowDefinition Height="Auto"></RowDefinition>
<RowDefinition></RowDefinition>
</Grid.RowDefinitions>


<views:MyRadDiagram Grid.Row="1" x:Name="diagram" GraphSource="{Binding}"
             IsSnapToGridEnabled="False"
IsEnabled="True"
             IsInformationAdornerVisible="False"
             IsConnectorsManipulationEnabled="False">
</views:MyRadDiagram>
</Grid>

[Stefan]

Hi Terry,

Thanks for your code snipet. However I was able to reproduce it simply by adding a RadDiagram and an item in it (see the code below) and also every time I add a item in the RadDiagram the VS 2012 switches the view to Design.

<Grid>
<telerik:RadDiagram>
<telerik:RadDiagramConnection />
</telerik:RadDiagram>
</Grid>

As Peter wrote we are aware of this bug, but we need more time to ivestigate it and find whether the issue is caused by the RadDiagram design-time support or by the VS 2012. This is why I logged it in our PITS where you can track its progress. Unfortunately at the moment we can't suggest a workaround.

All the best, Stefan
the Telerik team

[Terry]

Just thought I'd mention that the VS2012 Update 2 didn't seem to change this behavior