Hi,
I have this problem with Web Client trial controls that I can't get the Silverlight 3 ChildWindow object work with XamWebGrid.
The problem rises when I try to show a child window (ChildWindow.Show) when there is a visible XabWebGrid object on the parent window. I get InvalidOperationException with message "Cannot resolve TargetName contentPresenter.".
Hello,
There is no difference between trial and full version in the code of our controls. Does this mean that you have tried this on a full version control set and it is working correctly?
I am attaching a sample project using your steps to reproduce. Please take a look at it and let me know if you can reproduce the behavior that you are describing with this sample. If not, please modify it so that the problem is reproducible.
Hello,Than you for the answer. I investigated my code further and discovered that the error/bug is related to XamWebGrid pager. Just applying paging will reproduce the error.Here is what I added to your sample code to reproduce the error:<igGrid:XamWebGrid.PagerSettings><igGrid:PagerSettings AllowPaging="Both" PageSize="5"/></igGrid:XamWebGrid.PagerSettings>
I was able to reproduce this. This looks like an issue. I am going to create a support case for this on your behalf and continue the discussion there.
I have version 9.2.20092.2014 of Infragistics.Silverlight.v9.2 and Infragistics.Silverlight.XamWebGrid.v9.2 assemblies.
Error shows up when you set the group by expansion indicator as visible. This can be achieved by adding following code in the your previous sample project:
<igGrid:XamWebGrid.GroupBySettings> <igGrid:GroupBySettings AllowGroupByArea="Top" ExpansionIndicatorVisibility="Visible" /> </igGrid:XamWebGrid.GroupBySettings>
I just tested this with the latest service releases for 9.1 and 9.2 and it is working correctly - without any exceptions. This is also true with or without the styles which were used to go around this issue.
Can you reproduce the new issue with the sample I had provided? If you can, which is the exact builds that you are using (also pleas include information on you environment). If not, can you please modify my original sample and reattach it so that we can pinpoint the problem?
I found that there is same kind of problem with group by area expander control. If I set ExpansionIndicatorVisibility="Visible" in GroupBySettings the application will crash when a new child window is opened.
This seems to be caused by the same disabled visual state bug as the previously discussed error.
Thanks for good support, the visual state fix seems to work as temporary workaround for the issue. I'll use it while waiting for the service release