The xamWebDialogWindow causes the designer to throw an exception when this control is placed on a grid in blend 4 RC.
Please, make sure you have the latest service pack (2022) installed on your computer. This release is compatible with SL4.
Let me know if you can resolve the issue with it.
Yes, that is the version I have installed and am getting the error with.
Yes, here is the info:
XamlParseException: [Line: 0 Position: 0]
StackTrace
at MS.Internal.XcpImports.CheckHResult(UInt32 hr)at MS.Internal.XcpImports.FrameworkElement_MeasureOverride(FrameworkElement element, Size availableSize)at System.Windows.FramworkElements.MeasureOverride(Size availableSize)at System.Windows.FramworkElement.MeasureOverride(IntPtr nativeTarget, Single inWidth, Single inHeight, Single& outWidth, Single& outHeight)InnerException: None
Occurs in Expression Blend 4 RC with xamDialogWindow in any container (grid, border etc). Silverlight 4 project.
Also, when the dialog is in maximized with the "RestrictInContainer" flag set to true, the title bar disappears. The windows behaviors are also erratic when restricted to a container. With the flag set to false the dialog window seems to work fine.
The image above shows the dialog as placed on the grid at startup without manipulating it.
The above picture shows what happens when the corner is used to resize the grid. The top dissappears. It also gets anchored to the center of this grid row for some reason.
The above picture shows the result of clicking the maximize button on the window. the title bar dissapears and parts of the border.
Here's the blend 4 exception:
In my last post I said ...the corner was used to "resize the grid" I meant ..."resize the dialog window"
I'm sorry for the delay.
I've tried to reproduce the issue in a sample project using the RTM version and the latest service pack for version 10.1. Althought there are couple of known issue with Blend 4 Beta, I was not able to reproduce this exception when resizing the dialog window. From the screenshots it looks like the dialog window goes under the ribbon which is unexpected - it should be at the top.
Please modify the attached project with your setup so we can look into this issue.
Well, I cannot duplicate the exception in blend 4 with your project or mine. Perhaps MS published an update since last week that fixed the issue. Anyway, the only problem I have now is the titlebar and borders disappearing when the window is maximized while restricted to a container. I modified your project and put the dialog window in a single grid with no ribbon bar or anything else on the design surface and here's what it looks like.
Here is the xaml:
<
="SilverlightApplication1.MainPage"
="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
="http://schemas.microsoft.com/winfx/2006/xaml"
="http://schemas.microsoft.com/expression/blend/2008"
="http://schemas.openxmlformats.org/markup-compatibility/2006"
="clr-namespace:Infragistics.Silverlight.Controls;assembly=Infragistics.Silverlight.XamWebDialogWindow.v10.1"
="clr-namespace:Infragistics.Silverlight.Controls;assembly=Infragistics.Silverlight.XamWebRibbon.v10.1"
="d"
="400">
="White">
="True" />
>
</
Not sure why the xaml was spread out so much in that last post. Sorry about that.
I did get the exception again just after posting the last message but when I restarted blend it went away again and I haven't seen it since. So it could be a Blend issue.
I noticed something I thought was odd between my project and yours from inside blend. The properties for the DialogWindow are different between the two projects. With your project there are a Misc properties panel and a XamDialogWindow Properties panel. In my project there is only a Misc panel with all the Misc and XamDialogWindow properties in it. I thought this was very strange behavior but it could be Blend 4. Who knows.
The main issue is still the missing titlebar and borders since, the window is unusable when restricted to a container.
Yes, we are using the latest SL4 build.
I found a way to get around the display issue. By adding the dialog window dynamically from code it works as expected within the container and can be manipulated after that. It seems the issues I've been seeing only occur when the window is included on the form at design time.
I don't see anything wrong with your xaml snippet. You may check if your project is build on SL4 and also change the margin of the dialog window. I suspect that probably your project is running on an earlier build of SL4 so one option is to install the latest build.
I hope this will resolve the issue. Let me know the outcome.